8:19 Correction- 1. Readwriteonce: This allows only a single node to access the volume in read-write mode. Furthermore, all pods in that single node can read and write to such volumes. 2. Readwritemany: Multiple nodes can read write to the volume. 3. Readonlymany: This means that the volume will be in a read only mode and accessible by multiple nodes.
Your explanation is superb, request from my side please could you please explan in english that will be very helpful for south indian learners too. Thanks
Pvc is a request to use pv and related storage. resource: request a storage: 8Gi accessmodes: same as pv. Pvc is binded to pv that match it's condition and requirements. Pvc is specified mentioned inside pod.
one question! aapne bataya kii 1pv se sirf 1pvc he bind ho skta hai, to phir multiple pods same pv ke data ko kaise access krenge? (like phir to ReadWriteMany ya ReadOnlyMany possible ni hoga sirf ReadWriteOnce possible hoga). Please clarify.
Great question! In Kubernetes, while 1 PVC is bound to 1 PV at a time (ReadWriteOnce), multiple pods can access the same PV by sharing the same PVC. However, for multiple pods to write simultaneously (ReadWriteMany), the storage system needs to support it, like NFS. I'll cover this in detail in an upcoming video. Stay tuned!
No, a PV cannot be bound to PVCs in different namespaces in Kubernetes. PVs and PVCs are namespace-scoped, and each PVC is intended to be bound to a PV within the same namespace.
hi.. i heard many times, might be you have said the same thing for RWO and RWM... when checked the kubernetes page - i found the below points for access modes..- could you please clear this for me.. thanks in advance... ReadWriteOnce the volume can be mounted as read-write by a single node. ReadWriteOnce access mode still can allow multiple pods to access the volume when the pods are running on the same node. ReadOnlyMany the volume can be mounted as read-only by many nodes. ReadWriteMany the volume can be mounted as read-write by many nodes.
Please help us with your valuable feedback - forms.gle/E9r3xvTxnLPKz9Hw9
4 years ke baad is type ka teacher mile, aur ye sabse achha channel hai youtube pe, jitne bhi hai
Glad to hear that. Thanks
I've seen videos from other renowned youtubers, but your explanations were detailed yet simple to understand.
great job! keep going.
I have been recently watching this.. very good videos
beautifully explained!! Nana Janashaia ne b itna achhe se nahi bataya the way you taught me.. I will not forget it now
Thank you so much! I'm glad it was helpful.
Hi I like your video, you are genius. I appreciate your knowledge and creativity.
Thank you very much!
Awesome firstly you way is best and second you give detail knowledge without gettinb bored madam
Thanks for liking
Didi ek number explanation doya hain aapne 🙏⭐
i hope your explanation is very easy under stable to us Thanks for helping for keep growing in Dev ops Career
Yes mam thank you very much aese hi detail mai video dalte raho
Please keep uploading such informative videos!!!
Mam you are awesome. Thank you so much for this explanation.
Best Concept explanation ever!Please do videos on other devops tools.
i think one of best explanation present on yt
8:19 Correction-
1. Readwriteonce: This allows only a single node to access the volume in read-write mode. Furthermore, all pods in that single node can read and write to such volumes.
2. Readwritemany: Multiple nodes can read write to the volume.
3. Readonlymany: This means that the volume will be in a read only mode and accessible by multiple nodes.
Superb Explanation Riya. Worth watching. Thanks for Sharing. :)
awesome explanation , easy to understand.
this is first video i watched from this channel , i love this concept . thank u so much ❤❤❤❤❤
Glad you liked it!!
Very nicely and deeply explained. looking for more valuable topics .
Thank you.
You're welcome! I'm glad you found the explanation helpful. Stay tuned for more content!
Supper … easy to understand … Thank you for such great tutorial… I will share it in my group who wants to learn
Thank you for the kind words and recommendation! I appreciate your support.
kitni cute ho ma'am aap , itni pyaari si awaaz hai bs mann krta hai sunte jaao , aap hi motivation ho mere devops domain mei aane ki
You are very good at explanation on kubernates topic which is difficult
Thank you for the compliment!
You are really doing hard and very good work
I wish you get all the success in your life
Thanks
Thank you for your kind words and well wishes, it means a lot to me!
@@DevOpsProCould i create replicas for persistant volume claim
Your explanation is superb, request from my side please could you please explan in english that will be very helpful for south indian learners too. Thanks
We have an english channel too, link can be found in description box of any video. Where we upload videos in english.
Great explanation!!!
perfectly understandable. thank you
Best...best... simply best explanation 🔥
Thank you so much 😀
Soo beautifully explained....you are awesome ❤
Thank you so much 😀
Beautiful Explanation.
Great mam,,,very great explaning
Thanks a lot
Great content n animation
well explained🙌
Pvc is a request to use pv and related storage.
resource: request a storage: 8Gi
accessmodes: same as pv.
Pvc is binded to pv that match it's condition and requirements.
Pvc is specified mentioned inside pod.
Very nice explanation
Very nicely explained.. ❤❤
Thanks a lot 😊
Amazing video🎉. Keep doing the good work. ❤
Great Video
Superb tutorials madam
Thank you so much 🙂
Veryy nice explaination
Great video keep going on 💥
Nice Explanation Madam
i have subscribed ur channel tq
Very Good Content
Thanks
Nice explanation 🙌
Thanks 🙂
Very good madam super se upperrrrrr
Thanks a lot
Super mam
but this was nicely explained.. my all fear regarding pv and pvc is resolved... also learned new concepts which other trainers did not show
one question!
aapne bataya kii 1pv se sirf 1pvc he bind ho skta hai, to phir multiple pods same pv ke data ko kaise access krenge?
(like phir to ReadWriteMany ya ReadOnlyMany possible ni hoga sirf ReadWriteOnce possible hoga).
Please clarify.
Great question! In Kubernetes, while 1 PVC is bound to 1 PV at a time (ReadWriteOnce), multiple pods can access the same PV by sharing the same PVC. However, for multiple pods to write simultaneously (ReadWriteMany), the storage system needs to support it, like NFS. I'll cover this in detail in an upcoming video. Stay tuned!
10:40
It's RWM policy
It should allow the next pod to mount, right?
Awesome
Please provide video on HELM
Absolutely! Thanks for your suggestion! I'll definitely consider creating a video on HELM. Stay tuned for more valuable content!
its awesome @devopsPro keep doing
Thank You
Awesome!
Awesome :)
Thanks 😁
Very informative video please mam cover rbac helm cron job topic
Nice
thank you
Great 🎉🎉
Thanks 😄
awesomeness
thanks, a lot
Can one pv be bound to two different pvc which are in two different namespaces?
No, a PV cannot be bound to PVCs in different namespaces in Kubernetes. PVs and PVCs are namespace-scoped, and each PVC is intended to be bound to a PV within the same namespace.
Can you please share English version link of videos
We will upload english version of CKA series on DevOps Pro English Channel very soon. Stay tuned!
@@DevOpsPro okay riya
hi.. i heard many times, might be you have said the same thing for RWO and RWM... when checked the kubernetes page - i found the below points for access modes..- could you please clear this for me.. thanks in advance...
ReadWriteOnce
the volume can be mounted as read-write by a single node. ReadWriteOnce access mode still can allow multiple pods to access the volume when the pods are running on the same node.
ReadOnlyMany
the volume can be mounted as read-only by many nodes.
ReadWriteMany
the volume can be mounted as read-write by many nodes.
yes, you are right
How can I watch English videos?
#devopspro
Super explain
Thank you