Flux: Multi-tenancy Deep Dive
summary
Flux is shown running multi-tenant clusters where each tenant maps to one namespace and one Git repo, bootstrapped with Terraform into a central fleet repo; a demo creates tenant B, Terraform commits a dev/qa/prod YAML and Flux reconciles a guestbook app and TLS automatically. The system posts deployment results back to Git via a notification controller so Git shows commit status checks, and blue‑green cluster cutovers work without changing individual CI pipelines.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:22What is Flux
- 2:22Flux & Flagger Timeline
- 3:06My Journey
- 5:14Flux at Xenit
- 6:20Pre Flux
- 10:07Multi Tenancy
- 15:00Promotion Flow
- 23:03Multi-cluster Blue/Green
- 25:33Flux community
related talks
27mOrchestrating Multi-Tenancy Kubernetes Environments with Flux
39mEnhance Your Kubernetes Experience with GitOps & Flux
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
09mWelcome + Opening Remarks
27mHow to Achieve (Actual) GitOps with Terraform and Flux
33mMay the Flux Be With You: Tales From the GitOps Trenches
39mCreating A Landlord for Multi-tenant K8s Using Flux, Gatekeeper, Helm, and Friends
24mHosting Applications in the Real World