You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 15, 2022. It is now read-only.
This guidance assumes AKS with Managed Identity (Kubernetes Cloud Provider Identity). It leverages AAD Pod Identity to assign another Managed Identity (Key Vault Identity) to the Secrets Store CSI Driver. This all works.
As a:
Operator
I want:
Better Understanding of Kubernetes-Secrets-Store-CSI-Driver integration with Key Vault on AKS
So that:
I can better determine the best secrets solution in an MSI AKS implementation for handling service secrets.
Describe the solution you'd like:
Documentation around benefits of using CSI and comparison with FlexVolume.
Acceptance Criteria:
Describe alternatives you've considered:
Additional context:
Related to: #1197
Does this require updates to documentation?:
Yes
The text was updated successfully, but these errors were encountered: