Platform Engineering meet-up - Mar 7

Abstract

Disaster recovery (DR) is no longer optional—especially when dealing with stateful workloads in Kubernetes environments. In this talk, I’ll dive into how Portworx DR makes it easier to build a resilient infrastructure by enabling efficient disaster recovery strategies tailored for Kubernetes.

I’ll start by laying the foundation: why DR is important in today’s cloud-native world, what RPO (Recovery Point Objective) and RTO (Recovery Time Objective) mean in practical terms, and how they influence our recovery planning.

We’ll then explore the different DR models supported by Portworx—asynchronous and synchronous (Metro DR)—and how each fits specific business needs. I’ll also walk through the mechanisms behind failover and failback, and how Portworx automates and streamlines these processes. To bring everything together, I’ll demonstrate a real-world failover and failback scenario to show just how seamless Portworx DR can be in action.

Takeaways

• Understand the fundamentals of disaster recovery, why it’s critical, and how to implement it in Kubernetes environments
• Gain insight into DR strategies, best practices, and how to approach DR planning for your own clusters

Target Audience

• Software Engineers seeking a practical introduction to disaster recovery concepts and tooling
• Infrastructure engineers managing Kubernetes environments

Bio

Hi Rootconf! 👋 I’m Siddhant, currently working at Portworx (Pure Storage) via Infracloud Technologies. I’m part of the Disaster Recovery team, where we focus on building solutions that help businesses stay resilient in the face of unexpected failures.

Prev: Platform Engineering team @ DeepSource.