Kubernetes Storage Classes - Using NFS storage class for dynamic allocation of storage to pods.

A StorageClass is a Kubernetes resource that enables dynamic storage provisioning. The administrator configures the StorageClass, which can then no longer be modified. First the StorageClass is created, then the PersistentVolumeClaim and finally the Pod. When a PVC is created, Kubernetes creates a PersistentVolume and binds it to the PVC automatically, depending on the VolumeBindingMode used in the StorageClass configuration. These three Kubernetes objects are required to check the test case of a StorageClass.
Good understanding of how storageclass help kubernetes administrators in dynamically allocating and using storage for applications is must.
In this video we will cover:
00:00-12:25 - Understanding need of storage classes
12:26-17:40 - Installing & Configuring NFS Server
17:41-21:43 - Installing helm, nfs provisioner & StorageClass
21:44-21:18 - Creating Persistent Volume Claim for storage request from StorageClass
21:19-31:00 - Creating Deployment which uses PVC for data storage
Visit us - networknuts.net
Social - #networknuts

[@hedbergmicke]

I love your handwriting. Allso great video!

[@Ketzunouka]

23:09

[@jalandharbehera99]

I had so many doubt but you solved that…Thank you so much bro…But please make one video of EBS or EFS

[@denismota5014]

outstanding!!!

[@samuelho8873]

Thank you! Very clear and helpful explanation!

[@666Husky]

I finally understood that concept - thank you! :)

[@taiwoesoimeme2383]

Hello Bhai ,...Amazing Video ...But what if i am using share directly from a storage. Do i still need to install the nfs-provisional.

[@himanshimehta9746]

Thanks Sir🎉

[@yassineelamrani7206]

Can i install jupyterhub using this?

[@jalandharbehera99]

Please give the codes and steps so that we can practice for same bro🙏

[@666Husky]

Hmm...the PVs are bound to the pods running at any particular moment.
If you redeploy them, they will get a new identifier and new PVs are created, thus making the application running empty.
For instance:
I set up a Grafana installation, I connect my database and everything and build my dashboards.
If the Deployment gets deleted or the cluster rebooted, a new (and empty) PV would be provisioned, right?
How would I make sure the connection between the pods and the PV remains intact and the data remains accessible by my application?
Or would the creation of a PV by myself be a better solution?
Thank You!