Hello, please cloud you explain me the effect of storageClassName mentioned in . . .

Kubernetes
#1

Amel ECHEIKH EZAOUALI:
Hello, please cloud you explain me the effect of storageClassName mentioned in pv and pvc ? i created a static storage without create storage class and i can create pv and pvc with storageClassName
image.png

image.png
image.png748×411 13.9 KB

#2

AB:
I think storage class for cloud computing. I AWS, Azure we got different types of storage. Some are cheap and some are fast.

#3

Amel ECHEIKH EZAOUALI:
now, i’m able to create pv and pvc with filed storageClassName: manual defined in pv and pc yaml file without create a storage class because i’m not using a dynamic strorage

#4

Amel ECHEIKH EZAOUALI:
storageClass does not exist

#5

Nada Nour:
the storage class for the case of local storage is used to delay the binding of the volume until the pod is created

volumeBindingMode: WaitForFirstConsumer

this is the use case used for it

#6

Amel ECHEIKH EZAOUALI:
but the storage class doesn’t exist, i don’t create a storage class with this yaml

image.png
image.png1010×487 27.7 KB

#7

Amel ECHEIKH EZAOUALI:
i juste create pv and pvc with filed storageClassName: manual but really this storage classe object does not created

#8

cv:
if there exists a pv with the specified storage class, the pvc gets bound, else it will wait for the storage class to provision

#9

cv:
as long as the class name match it doesn’t matter, they get bound

#10

Amel ECHEIKH EZAOUALI:
okey thank you

#11

PP:
@Amel ECHEIKH EZAOUALI have you tried creating the storage class “manual” what it says?

#12

Amel ECHEIKH EZAOUALI:
I don’t create a sc