Skip to content

fix(k8s): acls as a set to prevent ordering issues #3241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Mia-Cross
Copy link
Contributor

Since the response of ListClusterACLRules has its rules sorted by IP, there have been issues when the actual order the rules were written in the Terraform file doesn't match the order from the API.
Turning the ACL rules to a set instead of a list should prevent those problems in the future.

Closes #3233

@Mia-Cross Mia-Cross self-assigned this Jul 31, 2025
@Mia-Cross Mia-Cross added the k8s Kubernetes Kapsule issues, bugs and feature requests label Jul 31, 2025
@Mia-Cross Mia-Cross marked this pull request as ready for review August 1, 2025 10:00
@Mia-Cross Mia-Cross requested a review from a team as a code owner August 1, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s Kubernetes Kapsule issues, bugs and feature requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

k8s_acl rules trigger changes at each run ( sorting issue? )
1 participant