Kubernetes Disaster Recovery (DR)

preview_player
Показать описание
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.

**Connect with me**

#kubernetes #disasterrecovery #cloudwithraj
Рекомендации по теме
Комментарии
Автор

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 YouTube, especially for on-premise setups, while cloud-based solutions are more commonly covered. Your guidance on these topics would be greatly appreciated. Thank you.

awssoorinje
Автор

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

CarlosSantanaDev
Автор

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

sharathsachin
Автор

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

sivabhimireddy
Автор

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.

leamon
Автор

Nice 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.

samimkumarpatel
Автор

I always love your content, very detailed explanation.

twizzoe
Автор

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.

dpkcapricorn