You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are there any examples that use the new Finalizer helper library? I'm giving it a try but don't quite understand where the business logic of the finalizer should live. It feels like the Reconciler knows what should be deleted, not main.
Should I define the finalizer logic inside the x_controller.go file, and just register that in the main? Should the reconciler itself actually implement the Finalizer interface?
And then, does it make sense to requeue if either the obj or its status was updated?
Finalizers could be used to clean up any external resources across namespaces when the parent object is deleted. This example maybe helpful to have an overview on where finalizers could be used inside a controller.
Are there any examples that use the new Finalizer helper library? I'm giving it a try but don't quite understand where the business logic of the finalizer should live. It feels like the
Reconciler
knows what should be deleted, notmain
.Should I define the finalizer logic inside the
x_controller.go
file, and just register that in the main? Should the reconciler itself actually implement theFinalizer
interface?And then, does it make sense to requeue if either the obj or its status was updated?
Thanks for the help!
Originally posted by @austince in #1453 (comment)
The text was updated successfully, but these errors were encountered: