-
|
What is the relation/difference between using the CSI driver from this repository vs. the AKS addon You can install the addon with this command: az aks create -n myAKSCluster -g myResourceGroup --enable-addons azure-keyvault-secrets-provider --enable-managed-identitySee https://docs.microsoft.com/en-us/azure/aks/csi-secrets-store-driver |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Hello 👋🏻 There is no difference between the 2. The AKS add-on is a managed offering of this project. AKS handles the deployment and upgrade of the driver and provider when enabled as an add-on. If you install the driver and provider manually using helm charts from OSS, it's not officially supported by Microsoft: https://github.com/Azure/secrets-store-csi-driver-provider-azure#support. For OSS, support is only via GitHub issues. Instead If you enable the add-on, it is supported and you can open support tickets if you have any issues. |
Beta Was this translation helpful? Give feedback.
Hello 👋🏻 There is no difference between the 2. The AKS add-on is a managed offering of this project. AKS handles the deployment and upgrade of the driver and provider when enabled as an add-on.
If you install the driver and provider manually using helm charts from OSS, it's not officially supported by Microsoft: https://github.com/Azure/secrets-store-csi-driver-provider-azure#support. For OSS, support is only via GitHub issues. Instead If you enable the add-on, it is supported and you can open support tickets if you have any issues.