-
Notifications
You must be signed in to change notification settings - Fork 135
fix: split EPP RBAC into cluster and namespaced scoped permission #1071
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
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
I think the test utils/suite need to be updated too: $ grep -ri ClusterRole .
./config/charts/inferencepool/templates/rbac.yaml:kind: ClusterRole
./config/charts/inferencepool/templates/rbac.yaml:kind: ClusterRoleBinding
./config/charts/inferencepool/templates/rbac.yaml: kind: ClusterRole
./config/manifests/inferencepool-resources.yaml:kind: ClusterRole
./config/manifests/inferencepool-resources.yaml:kind: ClusterRoleBinding
./config/manifests/inferencepool-resources.yaml: kind: ClusterRole
./test/testdata/metrics-rbac.yaml:kind: ClusterRole
./test/testdata/metrics-rbac.yaml:kind: ClusterRoleBinding
./test/testdata/metrics-rbac.yaml: kind: ClusterRole
./test/testdata/inferencepool-e2e.yaml:kind: ClusterRole
./test/testdata/inferencepool-e2e.yaml:kind: ClusterRoleBinding
./test/testdata/inferencepool-e2e.yaml: kind: ClusterRole
./test/e2e/epp/e2e_suite_test.go: // Wait for the clusterrole to exist.
./test/e2e/epp/e2e_suite_test.go: return k8sClient.Get(ctx, types.NamespacedName{Name: "pod-read"}, &rbacv1.ClusterRole{})
./test/e2e/epp/e2e_suite_test.go: // Wait for the clusterrolebinding to exist.
./test/e2e/epp/e2e_suite_test.go: return k8sClient.Get(ctx, types.NamespacedName{Name: "pod-read-binding"}, &rbacv1.ClusterRoleBinding{})
./test/utils/utils.go: binding := &rbacv1.ClusterRoleBinding{
./test/utils/utils.go: role := &rbacv1.ClusterRole{
./test/utils/utils.go: metricsReaderBinding := &rbacv1.ClusterRoleBinding{
./test/utils/utils.go: metricsReaderRole := &rbacv1.ClusterRole{
./Makefile:manifests: controller-gen ## Generate WebhookConfiguration, ClusterRole and CustomResourceDefinition objects.
...
./site-src/guides/metrics-and-observability.md:To scrape metrics, the client needs a ClusterRole with the following rule:
./site-src/guides/metrics-and-observability.md:kind: ClusterRole
./site-src/guides/metrics-and-observability.md:kind: ClusterRoleBinding
./site-src/guides/metrics-and-observability.md: kind: ClusterRole
... |
This will be a breaking change for implementations. @nirrozenbaum @kfswain @ahg-g we need a way to ensure breaking changes are highlighted when a release is cut. |
nit: Update comment from "ClusterRole" to "Role" or "RBAC":
/lgtm |
/lgtm |
how about adding a label (gie-area/breaking-change) and label the PR. then add instructions to whoever is doing the release to go over the list of PRs and highlight what's needed? |
We could also tag breaking PRs in a comment on the release tracking issue/milestone |
Raised a PR in test-infra to create a new label called |
anything pending on merging this PR? |
Added release note in the PR description. Nothing pending on merging this PR. |
Signed-off-by: Ernest Wong <[email protected]>
Signed-off-by: Ernest Wong <[email protected]>
@ahg-g @nirrozenbaum could you take another look? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, chewong The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
apiGroup: rbac.authorization.k8s.io | ||
kind: Role | ||
name: {{ include "gateway-api-inference-extension.name" . }} | ||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just making sure, was the helm chart tested and verified it's working?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested it again and encountered some issues. Opened #1274 to fix them.
…bernetes-sigs#1071) * fix: split EPP RBAC into cluster and namespaced scoped permission Signed-off-by: Ernest Wong <[email protected]> * New API group Signed-off-by: Ernest Wong <[email protected]> --------- Signed-off-by: Ernest Wong <[email protected]>
Fixes #224
Testing: