Kristian Sørensen Stene

Have you tried the multi key value secret sync covered i this tutorial https://akv2k8s.io/tutorials/sync/4-multi-key-value-secret/ ? Is this sufficient for your use case?

Could you provide some additional information such as: 1. Env-injector (webhook) version. 2. How you installed the tools (e.g. helm chart) and provide the chart values set (e.g. `values.yaml`). 3....

Could this be related? https://github.com/SparebankenVest/azure-key-vault-to-kubernetes/issues/162

The `"failed to validate credentials" status="403 Forbidden" ` is a result of a failed authorization of the request at the env-injector-webhook side after the pod env injector tries to validate...

The AWS credentials error is unrelated to this case. The webhook logs that you provided indicate that (i) the webhook is able to mutate the application container and update application...

Could this be related? https://github.com/SparebankenVest/azure-key-vault-to-kubernetes/issues/175

Great job finding a solution to your problem @muwiess! @pb586b Does this help in your case?

Thanks for reporting this @tehho. Just to clarify, It is the k8s secret's labels and/or annotations that gets overwritten by the the akv2k8s controller when syncing the AzureKeyVaultSecrets? This is...

Please check the Controller logs to obtain more information why it fails (https://akv2k8s.io/troubleshooting/controller-log/). This warning is often occur when akv2k8s do not have Get permission on the keyvault. Ensure that...

@ukreddy-erwin Did you find a solution to your problem?