We must not create the namespace nor operator group when gitOpsSubNamespace is empty or null#50
Merged
mbaldessari merged 2 commits intoMar 13, 2026
Conversation
…espace is empty or null
Otherwise the old operator with the new chart will try and actually push
the namespace + operatorgroup policies with names like this:
- complianceType: mustonlyhave
objectDefinition:
apiVersion: v1
kind: Namespace
metadata: {}
- complianceType: mustonlyhave
objectDefinition:
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: -operator-group
And they will never be compliant
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.
Otherwise the old operator with the new chart will try and actually push
the namespace + operatorgroup policies with names like this:
objectDefinition:
apiVersion: v1
kind: Namespace
metadata: {}
objectDefinition:
apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: -operator-group
And they will never be compliant