Cloud Climber:
Lightning labs - Q5, anyone have solved it guys?
SHANKAR NAG MACHIRAJU:
yes…
Vembaiyan:
Cloud Climber k describe pod/podname will give clue on error
SHANKAR NAG MACHIRAJU:
describe command will give you the reason for error
Balakumaar:
add storageclass in PVC
SHANKAR NAG MACHIRAJU:
can u send ur pvc yaml file…
A shivanand kumar:
before making any changes when u run k get pvc -n alpha already there will be an existing pvc with status pending due to incorrect accessMode,capacity and storageClass. modify the existing pvc with the same name a"alpha-claim" or delete and recreate, then it should bound to ur pv. now provide the claim details “alpha-claim” in pod definition file.
Balakumaar:
accessModes should be same
Balakumaar:
and and add the storageclass in PVC yaml file
Ravi Sharma:
accessModes, StorageClass and Capacity should match with PV.
I personally use diff command to differentiate both the files.
Cloud Climber:
guys, lets break it down a bit, first i see that the pod is waiting for another pvc, with different name, so step no1 is to rename the pvc to match the expectations of the pod correct?
Vishnu:
It happened to me as well, I think there is some with issue with either katakoda or kubeadm provisioned cluster. Restart the lab, delete the alpha-claim pvc first in alpha ns, create the pvc with name mysql-alpha-pvc, in alpha ns, it should now get bound to pv.
