docs: add the AKS workload-identity design - #63
Draft
ashish1099 wants to merge 1 commit into
Draft
Conversation
Secretless Azure access on AKS via the managed OIDC issuer : the existing Crossplane workload-identity composition is parameterized with an issuerURL input (skipping the storage-account issuer hosting), the webhook comes from AKS's securityProfile.workloadIdentity add-on, and everything runs day-2 in-cluster post-pivot — the self-managed chicken-and-egg doesn't exist on AKS. Consumers migrate in order : Velero (unblocks DR on AKS), then CAPZ's AzureClusterIdentity flips ServicePrincipal → WorkloadIdentity and the client secret rotates out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design doc only — no code. Proposes secretless Azure access on AKS clusters:
workload-identity-infrastructurecomposition with anissuerURLinput: AKS passes the managed issuer (AzureManagedControlPlane.status.oidcIssuerProfile.issuerURL, enabled since #171's chart work) and skips the storage-account issuer-hosting resources; self-managed behavior unchanged. One declarative owner for Azure IAM across both flavours.securityProfile.workloadIdentity.enabled) — the azure-workload-identity-webhook chart never deploys on AKS.AzureClusterIdentityflipsServicePrincipal→WorkloadIdentity— strictly gated on the federated credentials existing — and the client secret rotates out.Open items called out: exact CAPZ/ASO ServiceAccount subjects, Velero role scope narrowing, and how the
capiUAMI clientID reaches the chart values.