Multitenancy - Build Vs. “Buy”: Zcaler’s Journey
summary
Zscaler builds a GitOps-based multitenancy platform that replaces fragile GitHub Actions/SDK deployments with Kubernetes + Flux, Helm, Kustomize, Terraform, Vault, Git and LaunchDarkly, enabling tenant onboarding by adding a folder and offboarding by removing it with prune: true. Demo shows per-tenant namespaces, customer-specific Helm releases and Kafka topics spinning up on merge, reconciliation alerts and cost savings from eliminated “zombie” tenants, and CI checks using Flux diff to catch cluster-breaking changes before merge.
AI-written summary · about
chapters (11)
- 0:00ZScaler multitenancy journey intro
- 1:46Zscaler Posture Control overview
- 4:14Greenfield project decisions
- 8:25GitOps and Flux evaluation
- 9:49Demo repo structure
- 14:05Live tenant onboarding
- 15:56Multi-repo deployments best practices
- 17:22Flux CI/CD and monitoring
- 21:16Deployment learnings and pain points
- 26:15Wrap-up and resources
- 28:01Q&A on reconciliation intervals
related talks
27mOrchestrating Multi-Tenancy Kubernetes Environments with Flux
26mFlux: Multi-tenancy Deep Dive
39mCreating A Landlord for Multi-tenant K8s Using Flux, Gatekeeper, Helm, and Friends
35mKubernetes journey
39mEnhance Your Kubernetes Experience with GitOps & Flux
29mAccelerating GitOps Adoption with Flux
40mScaling Startup for Success: Building modern Architectures and Developer Acceleration
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux