Share via

New secrets from AKV not mounted into AKS pods

Anonymous 0 Reputation points
2024-12-05T17:15:40.5033333+00:00

Hello,

I have my secretproviderclass.yaml referencing all the secrets in the AKV, and I am using user-assigned managed identity along with the CSI secret store driver. Everything is working; however, when I add a new secret to the AKV reference it and restart the AKS pods, the new secretes are not pulled from the AKV. Could you please guide me how to resolve the issue? Please note that I am not setting "rotationPollInterval" since I don't change secrets very often and that will create overhead. I would appreciate your assistance with this matter.

Thank you.

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,205 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vahid Ghafarpour 22,290 Reputation points
    2024-12-25T19:37:19.5233333+00:00

    Ensure that your SecretProviderClass YAML file is correctly configured and references the new secrets. Double-check the mappings and paths to make sure they are accurate.

    In addition, Make sure that the user-assigned managed identity has the necessary permissions to access the new secrets in the Azure Key Vault (AKV). You can verify this in the Azure portal under the Key Vault's Access Policies.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.