Connecting the World: Your Hands-on Guide To Cilium ClusterMesh and MCS-API
summary
Demo shows a working GitOps deployment: two GCP clusters in separate VPCs managed by FluxCD, with kube-proxy replaced by Cilium, CoreDNS auto-configured, and service imports auto-created via MCS API. Cilium ClusterMesh provides a flat pod IP space and cross-cluster load balancing with up to 255 or 511 clusters depending on config. Network policies enforce cross-cluster isolation and Hubble surfaces policy denials. Recommend Cilium 1.19; demo validates DNS (cluster-set.local), service failover, and policy enforcement end to end.
AI-written summary · about
chapters (15)
- 0:00Cilium Cluster Mesh intro
- 1:03Multi-cluster networking challenges
- 2:51What is Cilium Cluster Mesh
- 3:54How it works
- 6:26Service load balancing options
- 7:29Global service vs MCS API
- 8:52MCS API deep dive
- 11:39Recent improvements
- 13:25Future features and security
- 14:49Sentry’s multi-cluster use case
- 18:45Demo setup and config
- 19:30Load balancing with MCS API
- 21:14Security with network policy
- 24:06Helm and Flux CD integration
- 25:16Q&A
related talks
32mBreaking Boundaries: Multi-cluster with Cilium cluster mesh
27mCilium Cluster Mesh: The eBPF-Powered Multicluster Solution for Kubernetes
31mCilium Mesh
27mSimplifying Multi-Cluster Networking With Cilium...
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
10mLightning Talk: Connecting Klusters on the Edge with Deep Dive into Cilium Cluster Mesh
27mMeshing It up Securely: How Roche Manages Network Connectivity for...
16mCilium Wars: Scaling Up Your Network with Jedi-like Cilium Handling Techniques - Yash Tandon