fix(controller): use ownerreferences without controller owner relation #1095
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the fundamental behavior regarding namespace reconcilation. I stumbeled across this while automating against a platform, which creates namespaces for each cluster and adds controller references to the namespace. Since you can only have one controller reference per namespace, such a setup won't work.
With this change, instead of reconciling on the namespaces which are owned by the controller, we reconcile all the namespaces which have a tenant ownerreference.