Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Minimal permissions required for running CAPZ #5426

Open
tjungblu opened this issue Feb 12, 2025 · 0 comments
Open

Minimal permissions required for running CAPZ #5426

tjungblu opened this issue Feb 12, 2025 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@tjungblu
Copy link

/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

az ad sp create-for-rbac --role contributor --scopes="/subscriptions/${AZURE_SUBSCRIPTION_ID}"

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:

  • cluster-api-provider-azure version: N/A
  • Kubernetes version: (use kubectl version): N/A
  • OS (e.g. from /etc/os-release): N/A
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 12, 2025
@nawazkh nawazkh added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
CAPZ Planning
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@k8s-ci-robot @nawazkh @tjungblu