Reconcile Routes and ZenExtension later #912
Merged
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.
Originating issue: PrivateCloud-analytics/Zen#39543
If Zen and IM were installed on the cluster at the same time, and the Zen front door was enabled on the Authentication CR, this would lead to IM waiting for the ZenExtension resource to be reconciled without standing up its Operands for Zen to register OIDC clients with.
This changes the order in which objects are reconciled so that Zen will be able to communicate with IM's Operands and create those OIDC clients, which will in turn allow the Zen Operator to handle the ZenExtensions that IM needs in order to expose its Operands to ingress traffic.