Kubernetes Persistent Data Challenges – AZ, Region and Multi-Clou...
summary
Demo runs on EKS with i3en NVMe nodes and a StorageOS CSI plugin backing Prometheus and Cassandra via the k8ssandra operator; cordon/drain and a terminated instance both show Prometheus keeps historical metrics because of storage-layer replication while Cassandra continues serving thanks to its app-level replication and the cluster auto-replaces the node. Multi-cluster prototype uses Aviatrix networking, k8ssandra control/data-plane pairing and gossip across GKE/AKS/EKS; networking, cross-cloud credentials, latency and egress costs are the real obstacles.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:06Availability Zones
- 26:50Control Plane
- 27:47Install the Client Configurations
- 31:56Difference between a Control Plane and a Data Plane
related talks
29mPre-cloud Cassandra to Multi-Cloud Kubernetes
31mAn Adventure in Multi Cloud with Kubernetes and Distributed Data
42mDistributed Data Stores on Kubernetes
41mAn Adventure in Multi-Cloud with Kubernetes
26mTaking Your Database Beyond the Border of a Single Kubernetes Cluster
57mSecure Kubernetes data management and scaling with Kasten K10
37mData On Kubernetes, Deploying And Running PostgreSQL And Patterns For Databases In a Kubernetes Cluster.
42mImproving Availability for Stateful Applications in Kubernetes
