docs: note ESO workload identity auth for Azure Key Vault env groups#378
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: note ESO workload identity auth for Azure Key Vault env groups#378mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Document that on AKS clusters with Workload Identity enabled and a federated cloud account, Porter now authenticates the External Secrets Operator to Azure Key Vault via Workload Identity Federation instead of a service principal secret.
Changes
Context
Upstream PR: porter-dev/code#6477 — feat: authenticate ESO to Azure Key Vault via workload identity. The change is automatic: when env groups sync to Azure Key Vault on an AKS cluster that has Workload Identity enabled and a federated cloud account, ESO now uses a Porter-managed UAMI + federated identity credential instead of a static client secret. The legacy service principal secret is removed from the workload cluster on the next sync. No API or CLI surface changes ship with this PR; the doc update simply tells users what authentication path is in use.
cc @jackowfish for review.