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!
Very good sts understand
thanks for sharing knowledge
23:09
I love your handwriting. Allso great video!
I finally understood that concept - thank you! :)
Thank you! Very clear and helpful explanation!
Could you also address ceph,rook,valero for DR,Backup,data management in next videos
I had so many doubt but you solved that…Thank you so much bro…But please make one video of EBS or EFS
Hello Bhai ,...Amazing Video ...But what if i am using share directly from a storage. Do i still need to install the nfs-provisional.
Thanks Sir🎉
outstanding!!!
Can i install jupyterhub using this?
Please give the codes and steps so that we can practice for same bro🙏
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!
You wanna to check out K8s statefulset.