[FEATURE] Vault name from configmap or secret about azure-key-vault-to-kubernetes

[torresdal]

Secrets and configmaps are namespace bound, so you would have to create secret/configmap for every namespace.

Compared to other native kubernetes objects, this would be the same as loading name of a deployment from a configmap. This is not common practice. I suggest you look at using templating for your requirement.

[kaktuspalme]

Thanks for your response and suggestion. I already use helm templates and values file if that's what you meant by using templates.

But that doesn't really solve the problem. I still have to adjust the values when applying the template on every cluster.

If you have a running service which depends on a secret. Later you have to add another secret, how do you update all the clusters with the new secret?
Edit: Every cluster points to another keyvault with the same keynames but different values.

But I know it's probably an uncommon edge case.

[torresdal]

I don't think we will support this in akv2k8s. When I mentioned templating, I was thinking more about Kustomize. We use it to handle different values for different environments, and I believe you could use it to point to different keyvaults in your AzureKeyVaultSecret's.

[kaktuspalme]

Probably I can solve it with Lookup Functions introduced in Helm 3.1.