More than any praise, may be this word puts a smile - 'Subscribed'!
@TechTutorialswithPiyush8 күн бұрын
Thank you 😊🙏
@bhanubisht8Күн бұрын
Completed the video...!!!!!
@dhruprajapati9269Ай бұрын
Just Amazing as all the videos of yours !! Thanks for this sir.
@TechTutorialswithPiyush28 күн бұрын
Thank you! Glad you're enjoying the series.
@abc-edmАй бұрын
thanks for your clear explanation, that made things easier and more fun
@TechTutorialswithPiyushАй бұрын
Awesome! I'm glad you found it fun and easy to understand. 😄
@ashutoshpandey61104 ай бұрын
Generally we don't need to change etcd manifest --> the mountPath and --data-dir location , as we know we --data-dir flag take from the mountPath location and mountPath location is linked with volume - hostPath ---So we just need to change the volume -> hostPath value that's it. Great tutorial
@khamruddin9884 ай бұрын
Thanks Piyush for your wonderful videos
@TechTutorialswithPiyush4 ай бұрын
You're most welcome
@harshgupta5113Ай бұрын
Awesome video
@TechTutorialswithPiyushАй бұрын
Thanks! 😊
@thejaswarup4 ай бұрын
Appreciate your efforts. Thank you.
@TechTutorialswithPiyush4 ай бұрын
Thanks for watching!
@baivabmukhopadhyay89702 ай бұрын
very informative.
@TechTutorialswithPiyush2 ай бұрын
Thank you!
@arunsippy2258Ай бұрын
you spoke about stopping the API server and ETCD POd before taking hte backup, but did not demonstrate it, or any doc related to that which u can suggest
@TechTutorialswithPiyushАй бұрын
I have explained that part in one of the previous videos. You can move the manifest yamls of these two components to a different directory from /etc/kubernetes/manifest and it will stop those
@Imran_kpk4 ай бұрын
Appreciate your efforts ❤
@TechTutorialswithPiyush4 ай бұрын
Thank you
@vijaykumar63704 ай бұрын
Super
@sundayuloko19644 ай бұрын
Thanks for sharing.
@TechTutorialswithPiyush4 ай бұрын
Thanks for watching!
@prashlovessamosa4 ай бұрын
Thanks Piyush
@TechTutorialswithPiyush4 ай бұрын
Welcome :)
@vijaykumar6370Ай бұрын
Hi , Could you pls explain about PEER etcd restore and backup. now a days they asked in CKA exam
@TechTutorialswithPiyushАй бұрын
Hello Vijay, peers are the members of an ETCD cluster in HA mode, you can still take the snapshot in the same way, to restore , you can to restore on each of the members by changing the value of --initial-advertise-peer-urls to the member IP. Rest all the process is same.
@ZahidKhan-hi1gb4 ай бұрын
So Beautiful Session ❤❤❤❤❤
@TechTutorialswithPiyush4 ай бұрын
Glad you found it helpful
@erdi0054 ай бұрын
Hi! I took my CKA exam yesterday, I got the question about ssh into node, and perform back up and restore of etcd with peer.key and peer.crt. If I passed those in when backing up, I received “no such file or directory” error on the peer.crt/peer.key. Any idea what to do here? Can’t find any examples out there that does this either. I also tried server.crt and server.key, but all I got was “permission denied”, so I suspect I have to authenticate with the peer flags somehow(?) These peer flags were also not present when checking the etcd pod’s commands. I do see in the docs, under Securing Communication that there are some peer flags for configuring etcd with secure peer comm., but these flags were unknown to the etcdctl tool
@TechTutorialswithPiyush3 ай бұрын
You might need to use sudo -i to elevate the privileges or use the command along with sudo, also, etcdutl tool, have you tried this?
@erdi0053 ай бұрын
@@TechTutorialswithPiyush Thanks for the answer, I passed the exam successfully and I was able to perform the entire backup and restore process with sudo, although it is not stated on the left that I should use sudo.
@TechTutorialswithPiyush3 ай бұрын
@@erdi005 Congratulations 👏🏽👏🏽 Yes, they should have mentioned this. Same happened with me as well
@erdi0053 ай бұрын
@@TechTutorialswithPiyush thank you for everything
@kunaldarji24033 ай бұрын
Hi, why we are giving new path as --data-dir to store backup file, backup already store in /opt/*.db path. can we use this path /opt/*.db path in etcd.yaml file? Pls explain on this
@TechTutorialswithPiyush3 ай бұрын
Can you please share the exact timestamp?
@kunaldarji24033 ай бұрын
@@TechTutorialswithPiyush - 21:22, "--data-dir="
@dips_073 ай бұрын
Hi Piyush need one clarification here 21:25 we are restoring the snapshot at new directory that is /var/lib/etcd-restore-from-backup right. But can we restore an etcd snapshot directly into the existing etcd data directory...if possible so we dont need to modify the etcd.yaml file...waiting for your response on this. Thaks in advance 🙏
@TechTutorialswithPiyush3 ай бұрын
Hello Buddy, Yes, we can restore it to existing directory as well but we are doing this to avoid overwriting the backup.
@KaushalBirthday1stjuly19923 ай бұрын
@@TechTutorialswithPiyush overwriting backup problem will come. Instead of that we can do below things: first we should check etcdutl and etcdctl working any location or not for this you can download etcdctl and etcdutl package binary and move its binary to /usr/bin/ after than remove folder etcd at location /var/lib/etcd now if you do etcdutl , you can do restore from snapshot... you don't need to do anything ...i have tried in killercoda exercise and its working... you can try it
@bhanubisht83 күн бұрын
Comment for target.....!!!!!
@guntreddirajesh4 ай бұрын
🤩
@marieswaran81248 күн бұрын
Is this etcd backup and restore method will restore secret, configmap with data or only object will be restored?
@TechTutorialswithPiyush7 күн бұрын
Yes, as the config data also get stored inside the etcd database
@marieswaran81247 күн бұрын
@@TechTutorialswithPiyush Thanks for the reply. I will practice it.
@LakshmiCharanTangisettiTangise6 күн бұрын
i have deployed ectd as a service not as a pod what is the process of taking etcd and backup i have tired ur process but not able to restore etcd can u please help
@TechTutorialswithPiyush6 күн бұрын
Hello, It should not matter how ETCD is deployed the process is same. Can you please share the steps you have followed and issue you are facing? It will be easy to troubleshoot if you can join the discord community (thecloudopscommunity.org) and share the details over there
@Imran_kpk4 ай бұрын
❤❤❤
@AsadOnline-sz3os4 ай бұрын
Krew plugin is required.. to smooth backup and restore
@TechTutorialswithPiyush4 ай бұрын
Plugins can be used for anything but we are learning things cloud native way. You can setup a cluster with just a few click in a managed cloud or just a single click using Terraform still, we need to understand how to setup from scratch. Our main goal is learning and that can be done by doing things the hard way.
@AsadOnline-sz3os4 ай бұрын
@TechTutorialswithPiyush thanks recently we migrated from 1.20 to 1.31 cluster and infact velerio is an option but somehow its fail to sync with new cluster. We did with using some plugins and it works like charm. And in vedio you were explaining through etcd is it work with some older version as well? Like 1.19 to 1.30? Thanks
@AsadOnline-sz3os4 ай бұрын
And through etcd method is it ensure having the same ingress gateway? Like the external ip.
@blitzerdisco2 ай бұрын
Hi Piyush! again thanks for your guidance on ETCD backup and restore, I learned a lot with your excellent pace in this course. There is one issue i encountered during the assignment. After performing the actions along with your video, i had the backup and restore successfully as you've shown. My cluster looked well. Then i followed the assignment steps and started by creating a new deployment. However pod creation and termination processes are halted with the etcd-restore-from-backup setting. after few hours of troubleshooting attempt - deleting calico pods etc, I managed to solve the problem by reverting the cluster from "etcd-restore-from-backup" setting to initial (original etcd) setup by modifying the etcd yaml. I think this would probably cause a downtime in a live system... In your case, would you be able to successfully create/terminate pods after the restore?
@blitzerdisco2 ай бұрын
ok, i tried again and this time it worked somehow :) i also tried to reproduce the problem but i couldn't make it :)) thanks anyway Piyush, you are welcome if you have any comments on this one.
@TechTutorialswithPiyush2 ай бұрын
I am super happy to know that you were able to fix the issue. That's how a devops engineer should work. You might have missed a step earlier but you did not give up, you tried again and fixed the issue, more learning and more understanding comes with that. More power to you