Replies: 1 comment 5 replies
-
It's still can be turned off, but in my opinion the possibility should be there. This contract of having there a finalizer or multiple finalizers comes from Kubernetes, will block deleting the resource, but the secondary operator will eventually remove it. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
While it makes sense to automatically generate finalizers for reconcilers handling custom resources, it might actually be dangerous to do so for reconcilers handling native Kubernetes resources as doing so might impact the cluster's behavior by preventing the cluster to delete resources it owns… What do people think?
Beta Was this translation helpful? Give feedback.
All reactions