fix(beekeeper): grant RBAC on traefik.io API group for Traefik v3 - #236
Merged
Conversation
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.
Traefik v3 (shipped by default in k3s >= 1.33) moved
IngressRoutefrom thetraefik.containo.usAPI group totraefik.io.The beekeeper ClusterRole only grants
get/list/watchon the legacy group, so on Traefik v3 clusters the beekeeper ServiceAccount cannot read IngressRoutes at all.Adding
traefik.ioalongside the legacy entry in the same rule covers both v2 and v3: RBACapiGroupsis a list, and a rule is the cartesian product ofapiGroupsxresourcesxverbs, so no separate rule is needed and the legacy group keeps working.The verbs are read-only, so this is no privilege escalation.
This is the RBAC counterpart to the resource-creation fix in #234 — that PR fixes the chart that creates the IngressRoute, this one fixes the chart that reads it. Those two were the only references to the legacy API group in the repo.
Chart version bumped 0.4.12 -> 0.4.13;
appVersionunchanged.