How to Make Your Kubernetes Add-Ons Management Painless in Multi Cloud
summary
Demo shows Velos running in a management cluster that declares per-cluster cluster profiles or namespace profiles to install Helm charts, raw YAML/JSON and policies to matched clusters; Flux is used only as a Flux source controller to sync Git repos. Velos templates values with Lua at deploy time to inject certificates and cross-cluster data, enforces deployment order and health via validate hooks, supports sharding and integrates with ExternalSecrets and Crossplane, and installs Cilium CNI and Kyverno policies end-to-end.
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
27mHow To Make Your Kubernetes Add-Ons Management Painless in Multi Cloud
14mManage Kubernetes Add-Ons for Multiple Clusters Using Cluster Run-Time State
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
20mDeliver a Multicloud Application with Flux and Carvel
01h 01mManaging Kubernetes the GitOps way with Flux
30mPolicy & GitOps Unite! Kyverno and Flux Save Cluster City
36mManaging Thousands of Clusters and Their Workloads with Flux
36mHow to make Kubernetes rhyme with prod readiness - Tiffany Jernigan and Matthias Haeussler