Closed pwc-sc closed 4 years ago
Following the steps to use a service principal, before you deploy your pod/deployment to a namespace, make sure kubectl create secret generic kvcreds
is created in the same namespace.
Closing this issue because of inactivity. Please feel to reopen if you are still having issues.
Describe the bug
Steps To Reproduce
Expected behavior Control the Volume mapping in a desired K8S namespace Key Vault FlexVolume version
Access mode: service principal or pod identity service principal Kubernetes version 1.15 Additional context Dear team using the instruction I was able to start a pod container and map the FlexVolume inside the pod using the service principal. Implicitly is working into K8S default namespace
How may I use the pods and deployments other then the default namespace , the only one available to mount the volume with the secrets from KeyVault at the moment
Kind regards Silviu Chiric