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

Update CAPI quick start for CAPZ 1.16 #4921

Closed
nojnhuh opened this issue Jun 12, 2024 · 2 comments · Fixed by kubernetes-sigs/cluster-api#10857
Closed

Update CAPI quick start for CAPZ 1.16 #4921

nojnhuh opened this issue Jun 12, 2024 · 2 comments · Fixed by kubernetes-sigs/cluster-api#10857
Assignees
@nojnhuh
Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.16

Comments

@nojnhuh
Copy link
Contributor

nojnhuh commented Jun 12, 2024

/kind documentation

The docs at https://cluster-api.sigs.k8s.io/user/quick-start.html show steps related to Service Principals which will not work as-is with the upcoming CAPZ 1.16 because of the new default to use Workload Identity (#4765). We should update the docs to either refer to steps to set up Workload Identity or with steps to modify the AzureClusterIdentity to use Service Principal.
@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 12, 2024
@nojnhuh
Copy link
Contributor Author

nojnhuh commented Jun 12, 2024

/milestone v1.16

@k8s-ci-robot k8s-ci-robot added this to the v1.16 milestone Jun 12, 2024
@mboersma mboersma modified the milestones: v1.16, next Jul 11, 2024
@mboersma mboersma added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jul 11, 2024
@mboersma mboersma modified the milestones: next, v1.16 Jul 11, 2024
@mboersma
Copy link
Contributor

/assign @nojnhuh

@nojnhuh nojnhuh mentioned this issue Jul 11, 2024
Merged
@nojnhuh nojnhuh moved this to In Progress in CAPZ Planning Jul 11, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in CAPZ Planning Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nojnhuh nojnhuh

Labels
kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
CAPZ Planning
Archived in project
Milestone
v1.16
Development

Successfully merging a pull request may close this issue.

📖 update Azure quick start for CAPZ v1.16 nojnhuh/cluster-api
3 participants
@mboersma @nojnhuh @k8s-ci-robot