Kubernetes Disaster Recovery (DR)

How do you achieve Kubernetes Disaster Recovery (DR). Amazon EKS control plane is highly available, and you can make your application running within a cluster highly available as well. Highly available means spanning across multiple availability zones within a single region. But this doesn't help you achieve multi-region resiliency, which is often the requirement for production applications. In this video we learn how to achieve that.
💰👨‍🎓 Get my courses with max discount and 30 day moneyback guarantee: bit.ly/3Eku9RH
🙏Please Subscribe: bit.ly/2Yk0Kbb
*Connect with me*
🤳 Instagram: / cloudwithraj
🏢 LinkedIN: / rajdeep-sa-at-aws
🐦Twitter: / cloudwithraj
#kubernetes #disasterrecovery #cloudwithraj

[@awssoorinje747]

Sir, Thank you for the informative lecture. Could you please make another video on setting up an on-premise Kubernetes cluster for both primary and DR sites? Additionally, please include an example of setting up a MySQL InnoDB cluster stretched across Kubernetes. A visual explanation would be sufficient, as a practical demonstration would take too long. There are very few resources on this topic available on KZbin, especially for on-premise setups, while cloud-based solutions are more commonly covered. Your guidance on these topics would be greatly appreciated. Thank you.

[@sharathsachin001]

Wonderful, thank you Raj. Please keep it coming about cloud and Devops new videos 🙏

[@cloudwithraj]

Thank you Sharath, I will

[@CarlosSantanaDev]

Great content Raj will be referring end users to this video explanation 🎉

[@cloudwithraj]

Ty Carlos. This means a lot since you are THE Kubernetes Pro. We gotta do another video soon

[@sivabhimireddy2283]

Nice content! We also use portworx with velero for the backup & restore ..

[@twizzoe]

I always love your content, very detailed explanation.

[@cloudwithraj]

I appreciate that!

[@leamon9024]

Great video! Is there any chance to talk about aws graviton which can be used in multi-arch docker container for better performance and more cost effective in AWS ECS/EKS/Lambda. Thanks Raj.

[@cloudwithraj]

Great suggestion! I will keep this in mind for future videos.

[@samimkumarpatel3805]

Nice Raj...... Networking by R53 and Global Acclerator. Database if Aurora or Rds need replication. What about Pods to replicate? You said Cluster Autoscaler and provisioner. Kindly carify.

[@utibeabasiumanah]

Cluster autoscaler will scale out the nodes. You can use a horizontal pod autoscaler to scale the pods in a deployment based on metrics like cpu and memory usage

[@rocktheworld1596]

Thank you

[@cloudwithraj]

You're welcome

[@2mahender]

We can use velero for eks backup

[@cloudwithraj]

Yes for the storage, I mentioned it.

[@dpkcapricorn]

Need help on this - multiple namespace running on single EKS cluster and i need billing of per namespace. There is no option in Billing dashboard to do so.

[@cloudwithraj]

Use Kubecost, free with EKS

[@dpkcapricorn]

@@cloudwithraj is it official? Safe to suggest on organisation level?

[@cloudwithraj]

@@dpkcapricorn Yes official, available in EKS marketplace