Moving from the Openstack Magnum to the Cluster API
summary
Compares running control planes as three VMs under OpenStack Magnum versus running control plane runs as pods in a service Kubernetes cluster, shows replacement of Heat/Magnum with Cluster API plus a custom Jelastic infrastructure provider (CAPGC), adds an OpenVPN proxy for kubelet and admission access and uses Argo CD recreates deleted infra for reconciliation, reports faster spinups, easier upgrades, visible kubectl status for clusters and machines, and adds bare metal worker support while eliminating per-cluster master VMs.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:37OpenStack Magnum overview
- 6:36Magnum pros and cons
- 11:37Cluster API overview
- 17:39Cluster API limitations
- 20:06Jelastic’s K8s architecture
- 25:20Observability improvements
- 27:31Magnum to Cluster API benefits
- 29:18Summary and Q&A
related talks
34mEffortless On-Premise Kubernetes: Cloud-Native Experience at a Fraction of the Cost
25mIntroduction To Cluster API
31mIntro: OpenStack SIG
36mUnderstanding Cluster-API Structure via the OpenStack Provider
41mHosted Control Plane on Kubernetes (HPC)
40mMay the Control Plane be with you: Kamaji and the rise of Kubernetes at scale
45mLarge-scale kubernetes deployment, which tools to use and how - Rachid Zarouali
31mDeclarative Underlays: Scaling Purpose-Built Infrastructure(Clusters)...