Zero Change Transitioning to Multi-Cloud Architecture
summary
Claims zero-change migration so apps and infra require no edits while moving to multi-cloud, using a Kubernetes-native control plane (karmada API server, scheduler, controllers) and policy CRDs like PropagationPolicy, OverridePolicy and ResourceBinding. Demo joins a member cluster, applies a ResourceTemplate then a PropagationPolicy, and shows automatic propagation, automatic HA spreading, override of image registry per-cluster, aggregated status from member clusters, and propagated resources being garbage-collected when deleted on the control plane. Source and issues on GitHub and Slack.
AI-written summary · about
chapters (5)
related talks
06mLightning Talk: Unifying Hybrid Clouds: A Journey Through Multi-Control...
36mKubernetes as the Universal Control Plane: From Pods to Multi-Cloud Infrastructure
36mThe Architecture of a Multi-Cloud Environment with Kubernetes
41mAn Adventure in Multi-Cloud with Kubernetes
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
51mEnabling Developers in a Multi-Cloud World
40mKubernetes is Your Cloud Control Plane
30mExtending Kubernetes Scheduler for Multi-Cluster and Multi-Cloud Workloads