HA and Data Mobility for persistent Volumes
summary
Provides a Kubernetes-native storage layer that consumes worker-node block devices (VMDK, EBS, LUNs) into a pooled abstraction, offers app-consistent snapshots and encryption via KMS, and replicates or migrates namespaces and PVCs between clusters using a cluster pair plus an S3-compatible object store for transfers. Requires Portworx Enterprise on both clusters and at least three worker nodes on the target; supports sync or scheduled async (example: every 5 minutes), uses Stork open source for orchestration, and offers resource transformations for cross-distro differences.
AI-written summary · about
chapters (16)
- 0:00Introduction and agenda
- 0:42Kubernetes journey phases
- 3:08Persistent storage challenges
- 3:49Portworx overview and design
- 7:23Storage classes and performance
- 8:05High availability in cluster
- 8:47Application consistent snapshots
- 10:33Encryption at rest
- 11:39Replication and disaster recovery
- 13:05Migration use cases
- 17:16Prerequisites for setup
- 19:02Cluster pair configuration
- 21:12Migration schedule setup
- 24:25Handling cluster differences
- 26:54Resource transformation
- 28:20Q&A session
related talks
34mData Management in Kubernetes – Backup, DR, HA
29mMoving & managing k8s persistent data across clusters and cloud
28mKubernetes Storage Evolution: Enabling High Performance Distributed Datastores
28mWant a VM with local storage? Fine, just try it with Hwameistor!
32mYour Pods can be stateless, your VMs cannot! How to manage state in k8s
24mSheng Liang, Rancher Labs & Murli Thirumale, Portworx | KubeCon + CloudNativeCon Europe - Virtual
24mCapacity-aware Dynamic Volume Provisioning For LVM-based Local Storage
33mPiraeus Datastore - Persistent Volumes for Kubernetes