Repository navigation
Cannot delete ShipwrightBuild object if operator was removed #70
Description
Activity
From grooming: @adambkaplan what would be the difference of this issue and #71 ?
@qu1queee this is a separate issue that occurs because the Shipwright operator adds a finalizer to the ShipwrightBuild object. If the operator is removed after a ShipwrightBuild object had been created, the ShipwrightBuild object may never get deleted from the cluster.
From grooming: the finalizer problem is a common problem with controllers in Kubernetes that get removed but objects with owned finalizers still exist. Documentation might be the only way to solve this.
Expected Behavior
If the Shipwright operator is removed, any ShipwrightBuild object should also be removed.
Actual Behavior
ShipwrightBuild objects remain (along with their related deployment of the Build controller). ShipwrightBuild objects cannot be deleted due to the finalizer placed on the
ShipwrightBuildobject.Operator Version
v0.9.0
/kind bug