-
Notifications
You must be signed in to change notification settings - Fork 209
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
Feature: Built-in roles for Azure Service Operator #2051
Comments
We should be able to do this with Kubernetes RBAC. We just need to define what roles are interesting. Do we want one per CRD type (I think we can Kubebuilder that). Or do we want some overarching ones? What are they though? |
This is 50% documentation and 50% us defining roles. |
We'll leave this issue open but interested in user scenarios/need before we implement it probably. |
No status change from above. |
We still want this - no major status change from above. |
No changes from above |
Still sorta interested in this but there really hasn't been much user clamor for it. |
Still interested. |
Today, the Azure Service Operator treats all requests from all users the same. To avoid accidental changes to resources, operators should be able to define different users and roles to use with Azure Service Operator. This will result in users being able to update resources through ASO in a way that's consistent with their permissions in other Azure entry points (CLI, Portal, etc).
The text was updated successfully, but these errors were encountered: