Require Gateway APIs for related perms and release 2.8.1 #595
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.
What this PR does / why we need it:
Only create Gateway APIs rules in RBAC roles if Gateway API CRDs are present on the cluster. This avoids installation failures when installers lack super-admin, and will not have permission to create roles that can access these resources.
Releases 2.8.1 with this and the other pending hotfix.
Kubernetes RBAC limits the role creation permission to creating roles that the account used to create the role already has itself. Roles are very unlikely to include permissions for Gateway APIs if Gateway API CRDs are not installed.
Reported in community Slack channel https://kubernetes.slack.com/archives/CDCA87FRD/p1652461006349149
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
main
branch.