Platform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
summary
Demo shows a practical GitOps control plane built on kind and vcluster where clusterctl exports manifests and Flux reconciles them so Flux manages clusters from a single management cluster. Self-service cluster creation becomes a single-file pull request by switching from raw YAML to a Helm release as cluster template that supplies values for tenant and cluster settings. Demo notes Helm nested-value limitations, suggests CI for bootstrapping, and flags remaining work on security, auth, and production-grade hardening.
AI-written summary · about
chapters (9)
- 0:00Platform engineering with GitOps
- 1:02Multi-cluster management with kind & vcluster
- 2:37Automating cluster creation with Flux
- 5:10Bootstrapping Flux self-management
- 7:40Control plane repositories for GitOps
- 9:43Self-service with Helm charts
- 12:20Rebuilding clusters for speed
- 13:34Tenants and advanced GitOps patterns
- 14:25Q&A
related talks
27mOrchestrating Multi-Tenancy Kubernetes Environments with Flux
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
26mFlux: Multi-tenancy Deep Dive
39mEnhance Your Kubernetes Experience with GitOps & Flux
24mHosting Applications in the Real World
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux
26mGitOps Lifecycle Management
33mKubernetes As A Service with GitOps