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
If the flux controllers are used in downstream operators, those operators can (should) create the flux resources with owner references. If used in this way, by not reconciling resources with owner references by default, we can prevent controller contention over the flux resources.
The text was updated successfully, but these errors were encountered:
This would not fit well with all use cases in which someone may take ownership of a resource. For example, another controller generating resources on behalf of a user based on templates while registering an owner reference to handle garbage collection (the right way).
Which is something we would like to support out of the box; without it creating configuration hurdles.
If the flux controllers are used in downstream operators, those operators can (should) create the flux resources with owner references. If used in this way, by not reconciling resources with owner references by default, we can prevent controller contention over the flux resources.
The text was updated successfully, but these errors were encountered: