Skip to content

Automate kind + workload identity #4763

@jackfrancis

Description

@jackfrancis

⚠️ 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/proposalIssues or PRs related to proposals.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.size/LDenotes a PR that changes 100-499 lines, ignoring generated files.

    Type

    No type

    Projects

    Status

    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions