Mervin Andres:
does any one can give me clue in this? cant figure out where to change either on the pod or in the pvc. Can’t bound the pvc to pv
Tej_Singh_Rana:
Hello, @Mervin Andres
Instead of changing in the pod, you can create new pvc, specified in the pod.
Tej_Singh_Rana:
We don’t have to do any changes in the PV. Just match the available fields in the PV, write according to that in PVC.
Tej_Singh_Rana:
like accessModes, storageClassName, resources, etc…
Tej_Singh_Rana:
To know the PV fields:
kubectl get pv <pv-name> -oyaml
Tej_Singh_Rana:
pv is not a namespace scoped so we don’t need to mention namespace.
Tej_Singh_Rana:
but in the case of PVC, we have to add namespace.
Tej_Singh_Rana:
kubectl get pvc <pvc-name> -n <namespace-name> -oyaml
Mervin Andres:
i tried it already, I write the resources that match on pv. but when I look at pv still on an available state. It should be on a bound state right before i can configure the pod right?
Tej_Singh_Rana:
Yes, after that it should be in bound state.
Tej_Singh_Rana:
Have you mentioned namespace in the pvc definition file?
Mervin Andres:
`this is what ive did
Mervin Andres:
but still the pv is on the available state
Tej_Singh_Rana:
I think you missed to write the same name of storageClassName.
Tej_Singh_Rana:
Don’t mention namespace with PV.
Tej_Singh_Rana:
In the pvc, you wrote storageClassName - slow-storage, in the pv, storageClass - slow
Mervin Andres:
it works thanks a lot