Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods.
When there is a root cause like this happening to an incident, it is a disaster to find it out.
(The reason I submitted this feature request is because it happened recently. We just had no where out at the time until we find the "space-like" thing when manually opened the yaml with VSC. The issue kept for 3 days.)
Anything else you would like to add:
N/A
Environment:
Secrets Store CSI Driver version: (use the image tag): v1.4.2
Azure Key Vault provider version: (use the image tag): v1.5.1
Describe the solution you'd like For example, there is a yaml file as below, and it should be rejected:
When there is a root cause like this happening to an incident, it is a disaster to find it out. (The reason I submitted this feature request is because it happened recently. We just had no where out at the time until we find the "space-like" thing when manually opened the yaml with VSC. The issue kept for 3 days.)
Anything else you would like to add: N/A
Environment:
kubectl version
): 1.28.3