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

Automate kind + workload identity #4763

Open
jackfrancis opened this issue Apr 22, 2024 · 0 comments · May be fixed by #4765
Open

Automate kind + workload identity #4763

jackfrancis opened this issue Apr 22, 2024 · 0 comments · May be fixed by #4765
Labels
kind/proposal Issues or PRs related to proposals. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Milestone
v1.16

Comments

@jackfrancis
Copy link
Contributor

⚠️ Cluster API Azure maintainers can ask to turn an issue-proposal into a CAEP when necessary. This is to be expected for large changes that impact multiple components, breaking changes, or new large features.

Goals

  1. Goal 1
  2. Goal 2

Non-Goals/Future Work

  1. Non-Goal 1
  2. Non-Goal 2

User Story

As a developer of CAPZ I would like to automatically use workload identity for all my feature work.

Detailed Description

[A clear and concise description of what you want to happen.]

Contract changes [optional]

[Describe contract changes between Cluster API Azure Provider controllers, if applicable.]

Data model changes [optional]

[Describe contract changes between Cluster API Azure Provider controllers, if applicable.]

/kind proposal
@k8s-ci-robot k8s-ci-robot added the kind/proposal Issues or PRs related to proposals. label Apr 22, 2024
@jackfrancis jackfrancis added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 22, 2024
@nojnhuh nojnhuh linked a pull request May 6, 2024 that will close this issue
CI: workload-identity native #4765
Open
4 tasks
@dtzar dtzar added this to the v1.16 milestone May 16, 2024
@dtzar dtzar added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 16, 2024
This was referenced May 30, 2024
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/proposal Issues or PRs related to proposals. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
CAPZ Planning
Status: In Progress
Milestone
v1.16
Development

Successfully merging a pull request may close this issue.

CI: workload-identity native jackfrancis/cluster-api-provider-azure
3 participants
@jackfrancis @dtzar @k8s-ci-robot