-
Notifications
You must be signed in to change notification settings - Fork 474
Minimal permissions required for running CAPZ #5426
Copy link
Copy link
Closed as not planned
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.
Description
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/backlogHigher priority than priority/awaiting-more-evidence.Higher priority than priority/awaiting-more-evidence.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
/kind feature
Describe the solution you'd like
Currently the quickstart uses the Contributor role, which is very broad:
cluster-api-provider-azure/docs/book/src/getting-started.md
Line 51 in 2a14a61
It would be great if there could be a custom (or even builtin) role that contains all required permissions for running capz in production.
Environment:
kubectl version): N/A/etc/os-release): N/A