federation: skip OperatorGroup creation when one already exists#4036
Closed
lmiccini wants to merge 1 commit into
Closed
federation: skip OperatorGroup creation when one already exists#4036lmiccini wants to merge 1 commit into
lmiccini wants to merge 1 commit into
Conversation
OLM enforces a single OperatorGroup per namespace. When deploying on OpenShift with the architecture repo, the namespace already has an OperatorGroup, and creating a second one prevents InstallPlan generation for all Subscriptions in that namespace. Check for an existing OperatorGroup before rendering the template and conditionally skip creation. This fixes multiregion deployments while preserving CRC support where no OperatorGroup pre-exists. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
OLM enforces a single OperatorGroup per namespace. When deploying on OpenShift with the architecture repo, the namespace already has an OperatorGroup, and creating a second one prevents InstallPlan generation for all Subscriptions in that namespace.
Check for an existing OperatorGroup before rendering the template and conditionally skip creation. This fixes multiregion deployments while preserving CRC support where no OperatorGroup pre-exists.