-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecretProviderClass
Correct create the Secret
but the mounted volume is empty
#1103
Comments
I have the same. Vault-csi-provider say that secret added to mount csi-secrets-store also without error |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Seeing the same exact behavior as described by @FirelightFlagboy Vault CSI provider:
Mount exists, but there are no files created. Valut: v1.16.1 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
What steps did you take and what happened:
I've configure
vault-provider
like sokube-cluster/helm/vault.yml
contain the following data:Then I config the
auth/kubernetes
entrypoint onvault
I've configure
secrets-store-csi-driver
using thehelm
chartI've created a
SecretProviderClass
like soI've configured a
Pod
like soInside the pod (
kubectl exec -it test-foo -- sh
), the mounted volume/secrets-store
remain empty but the env variable is set to the correct value:What did you expect to happen:
I expect the mount-point to populated with the secrets data.
Anything else you would like to add:
When inspect the logs, I've found a
Warning
but it seems to be raised only when I delete the pod.Which provider are you using:
I'm using an external
Vault
server as a providerEnvironment:
kubectl version
): 1.25.3The text was updated successfully, but these errors were encountered: