From Region To Multi-AZ: Building Resilient Cloud Infrastructure With OpenStack, Kubernetes, and OVN
summary
KT Cloud builds KCP—an OpenStack-on-Kubernetes platform (launched June 29) that uses OpenStack on Kubernetes with three role clusters (admin, management, stack), a shared OVN common network, Ceph/RBD mirroring or object backends for images, and Cluster API for lifecycle. Two AZs in Seoul ~30 km apart run a stretched, active‑active cluster over a dedicated WonIDC link with Geneve overlays; a distant region ~200 km away serves as multi‑region DR with manual Keystone failover and optional satellite quorum for voting. Trade‑offs: traffic locality, replication latency, and operational complexity.
AI-written summary · about
chapters (5)
- 0:00Cloud service provider worldview
- 7:26Disaster recovery constraints
- 12:26Multi-region vs multi-AZ
- 20:58Multi-AZ with stretched clusters
- 30:48Resilient cloud lessons
related talks
45mMulti-Kubernetes, Multi-Region — Help!
01h 12mOpenStack brings Kubernetes to the Edge
26mRun your Kubernetes cluster on OpenStack in Production
33mMulti-tenant K8s Networking with Kube-OVN
41mAn Adventure in Multi-Cloud with Kubernetes
39mThe Multi-Tenant Supercluster Approach
33mWhat We’ve Learned Building a Multi-Region DBaaS on Kubernetes
17mManaged Kubernetes Service for Public Cloud with Openstack and Kubernetes