Deploying a Service Mesh at Enterprise Scale With Consul
summary
Consul Enterprise 1.11 introduces admin_partitions: true to run a central Consul control plane with multiple tenant partitions, each declared by a partition name in client Helm values; demo uses three GKE clusters (one server cluster, two tenant clusters) with gossip/rpc exposed so clients join the central plane. Services and Kubernetes namespaces sync only into their partition scope, enabling per-tenant service mesh and config while upcoming partition scope gateways add controlled cross-partition communication. Alpha release available.
AI-written summary · about
chapters (9)
- 0:00Introduction to talk
- 0:28Common Consul deployments
- 2:35Multi-tenant challenges
- 5:45Admin partitions overview
- 7:32Demo setup
- 10:02Deploying in tenant one
- 11:52Partition isolation
- 12:55Deploying in tenant two
- 13:36Future enhancements
related talks
20mDesigning a Multitenancy Kubernetes Strategy That Fits Your Org
41mPolicy-based management of hundreds of Kubernetes clusters
26mMulti-Tenant vs Micro-Clusters in Kubernetes-Driven Platform Engineering
41mAbstractions on Abstractions, Are You Building for Kubernetes?
25mBuilding Multi-Cloud Service Meshes at Snowflake
26mIf You Build It, They Will Come - a Platform Modernization Journey
30mHow to Coordinate Your Multi-cluster Kubernetes Environment with Ease
35mMulti-Cluster Management Made Easy - Tsahi Duek and Dima Breydo