-
Notifications
You must be signed in to change notification settings - Fork 868
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
PV not being created upon provisioning - resulting in Vault Pod being stuck in pending state #936
Comments
Same exact issue with me running Kubernetes 1.27 and latest vault-helm version. |
Update: An |
can you please share detailed steps to fix this issue.. i am using k8s version 1.28 and trying to install vault using helm chart.. NAME READY STATUS RESTARTS AGE kube@k8s-master1:/opt/vault/vault-production$ kubectl describe pvc data-vault-prod-0 -n vault Normal FailedBinding 14m (x62 over 30m) persistentvolume-controller no persistent volumes available for this claim and no storage class is set |
This error also occurs on microk8s. It works on minikube, though. |
Is there any solution to this? |
I had the exact same issue. you need to:
then you can install vault or any other app that requires persistent volumes (the above is for using EBS, but is true for EFS or other data storages as well) |
Describe the bug
Upon Helm deployment using the values referenced below, there doesn't appear to be a PV being deployed alongside the PVC (not bound). This is resulting in the Vault pod being stuck in a pending state.
To Reproduce
Any deployment including the following Helm values -
Other useful info:
Pod -
vault-0
PVC -
data-vault-0
PV
Expected behavior
Vault PV being provisioned during the Helm deployment. Resulting in the Vault pod
vault-0
not being stuck inpending
status and being accessible.Environment
EKS - 1.25
vault-helm version:
version: "0.25.0"
Chart values:
The text was updated successfully, but these errors were encountered: