Dedicated Cluster management using Cluster API and Kube-Bind
summary
Shows a working pattern that provisions real clusters via Cluster API (using clusterctl and kind for local consumers) and exposes selected CRDs from a provider cluster with kube-bind so controllers run only on the provider. A kube-bind CLI creates a connector and a dedicated namespace per consumer; empty CRDs land in the consumer, resources applied there are synced back to provider controllers and status is mirrored. Demo confirms the sync model and tighter access isolation versus VPC peering.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06Cluster API overview
- 3:15Cluster API providers
- 7:49Cluster creation with Cluster API
- 9:35Accessing clusters securely
- 12:04Kube-Bind explained
- 14:52Resource syncing flow
- 15:58Acknowledgments and thanks
related talks
30mBuild Your Own Cluster API Provider the Easy Way
34mBuilding a Cluster Management API using Kubicorn
32mCluster API as Code
35mSimplified Experience Of Building Cluster API Provider In Multitenant Cloud
26mWriting Kubernetes Controllers for CRDs: Challenges, Approaches and Solutions
01h 24mTutorial: So You Want To Develop a Clust...
36mUnderstanding Cluster-API Structure via the OpenStack Provider
29mMulticluster Kubernetes Management Made Easy With Open Cluster Management