-
Notifications
You must be signed in to change notification settings - Fork 356
deploy: split out RBAC, fix leadership election permissions #156
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
The RBAC definitions were not updated when introducing leadership election, which depends on the permission to modify endpoints in the current namespace. Having the RBAC definition in a separate file makes them usable as-is elsewhere without manual editing, for example in kubernetes/e2e.
This rbac.yaml file is identical to the one in the E2E PR kubernetes/kubernetes#69868 |
The testing was done with the 0.4 release. If I haven't missed something, the provisioner still uses endpoints. The change to use configmaps as in the external-attacher will have to update the rbac.yaml together with the code. |
/lgtm |
2 similar comments
/lgtm |
/lgtm |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, pohly 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 |
Bump version of csi-translation-lib to master to include translation lib for Azure Disk/File, updates for AWS, GCE, OpenStack
The RBAC definitions were not updated when introducing leadership
election, which depends on the permission to modify endpoints in the
current namespace.
Having the RBAC definition in a separate file makes them usable as-is
elsewhere without manual editing, for example in kubernetes/e2e.