Does any one can give me clue in this? cant figure out where to change either on . . .

Kubernetes
#1

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
image.png

#2

Tej_Singh_Rana:
Hello, @Mervin Andres
Instead of changing in the pod, you can create new pvc, specified in the pod.

#3

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.

#4

Tej_Singh_Rana:
like accessModes, storageClassName, resources, etc…

#5

Tej_Singh_Rana:
To know the PV fields:

kubectl get pv <pv-name> -oyaml
#6

Tej_Singh_Rana:
pv is not a namespace scoped so we don’t need to mention namespace.

#7

Tej_Singh_Rana:
but in the case of PVC, we have to add namespace.

#8

Tej_Singh_Rana:

kubectl get pvc <pvc-name> -n <namespace-name> -oyaml
#9

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?

#10

Tej_Singh_Rana:
Yes, after that it should be in bound state.

#11

Tej_Singh_Rana:
Have you mentioned namespace in the pvc definition file?

#12

Mervin Andres:
`this is what ive did
image.png
image.png

#13

Mervin Andres:
but still the pv is on the available state

#14

Mervin Andres:

image.png
image.png1151×167 5.73 KB

#15

Tej_Singh_Rana:
I think you missed to write the same name of storageClassName.

#16

Tej_Singh_Rana:
Don’t mention namespace with PV.

#17

Tej_Singh_Rana:
In the pvc, you wrote storageClassName - slow-storage, in the pv, storageClass - slow

#18

Mervin Andres:

image.png
image.png874×162 4.76 KB

#19

Mervin Andres:
it works thanks a lot