'tag_cluster' policy applying kubernetes.io/cluster/<name>=owned to Hypershift SG’s#976
Merged
Conversation
ebattat
reviewed
Mar 12, 2026
ebattat
reviewed
Mar 12, 2026
ebattat
reviewed
Mar 12, 2026
ebattat
reviewed
Mar 16, 2026
ebattat
reviewed
Mar 16, 2026
ebattat
approved these changes
Mar 19, 2026
ebattat
left a comment
Member
There was a problem hiding this comment.
Pls check if we can add any test to cover this scenario before merging
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
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.
Type of change
Note: Fill x in []
Description
The ‘tag_cluster’ policy added kubernetes.io/cluster/ = owned to all security groups in a cluster. In Hypershift only the load balancer SG should have this tag; adding it to node/control-plane SGs broke cluster behavior.
Added a filtering so the policy excludes applying the cluster prefixes in the tagging.
For security reasons, all pull requests need to be approved first before running any automated CI