I think, nfs binding issue can be more of permission related. After waiting for coupl eof minutes, my pod got bind to pvc. It takes some time to pod to bind to pvc.
Is anything fundamentally that I am doing wrong here? When using hostPath volume, everything works fine. PV and PVC are bound correctly but statefulset shows above error. I tried using local volume also but again same error.
Pod has unbound immediate PersistentVolumeClaims I got it corrected and now my pvc is shown as bound. One issue was that accessmode of pvc was different from accessmode of pv. What can I check more to get it working?Ĭan it be related to nfs server and path (if by chance, it is mentioned incorrectly), though I see pv created successfully. I also tried setting storageclass as "" in pvc and not mention it in pv, but it did not work also. This time, I get below error: no persistent volumes available for this claim and no storage class is set I tried not giving any storageclass (did not create it) and removed it from pv and pvc both altogether. When I get the pvc events, it shows: Warning ProvisioningFailed 3s (x2 over 12s) persistentvolume-controller no volume plugin matched Now, when I try to deploy it, I get the following error on statefulset: pod has unbound immediate PersistentVolumeClaims Statefuleset has following pvc section defined: volumeClaimTemplates:
Provisioner: kubernetes.io/no-provisioner My pv, pvc and sc configs are as below: kind: StorageClass
#Pod has unbound immediate persistentvolumeclaims install
I am trying to install elastic search cluster with statefulset and nfs persistent volume on bare metal. I know there are lots of discussions round this topic but somehow, I can not get it working.
0 kommentar(er)
