How to Make Your Kubernetes Add-Ons Management Painless in Multi Cloud
summary
Velos runs in a management cluster and uses the Flux source controller to pull manifests, then pushes Helm charts, raw YAML/JSON and Kustomize outputs to selected clusters via cluster profile selectors. The demo shows Cilium deployed as the CNI to two labeled clusters with different versions, then Kyverno policies applied only after a Lua-based validate health check reports ready. Templates pull per-cluster certs from configmaps in the management cluster and the described deployment flow succeeds in the presented demo.
AI-written summary · about
chapters (11)
- 0:00Kubernetes add-ons in multicloud
- 1:03Multicloud Kubernetes challenges
- 5:36What is VELERO
- 8:06VELERO for add-ons
- 13:00Cluster profiles deployment
- 15:06Demo: Deploy Cilium CNI
- 21:46Templating with VELERO
- 24:56Deployment order validation
- 27:00Demo: Deploy Karmada policies
- 29:54VELERO resources community
- 30:37Q&A
related talks
07mOptimizing Kubernetes Multicluster Backup & Restore
37mBuilding a Managed Platform While Maintaining a Good Developer Experience
10mKeynote: Multi-Cloud and Multi-Cluster with CNCF’s Kuma on Kubernetes and VMs
41mPolicy-based management of hundreds of Kubernetes clusters
24mWe Broke Free From Cloud-Managed Kubernetes...
24mBeyond Tool Sprawl: An Event-Driven Approach to Dynamic Multi-Cloud Operations
36mKubernetes Multi-Cluster Made Easy - Federica Ciuffo and Marco Ballerini
36mResilient Multi-Cloud Strategies: Harnessing Kubernetes, Cluster API, and Cell-Based Architecture