Connect multiple Kubernetes clusters across different cloud providers using Cilium Cluster Mesh for seamless cross-cluster workload communication.
Cilium Cluster Mesh provides:
- Cross-cluster service discovery
- Shared service load balancing
- Network policy enforcement across clusters
- Transparent encryption
| Use Case | Description |
|---|---|
| Multi-cloud resilience | Run workloads across Hetzner + Azure for redundancy |
| Geographic distribution | Place clusters close to users in different regions |
| Cost optimization | Use cheaper providers for burst capacity |
| Hybrid cloud | Connect on-premises with cloud providers |
| Migration | Gradually move workloads between clusters |
┌─────────────────┐ ┌─────────────────┐
│ Hetzner Cluster │◄──────►│ Azure Cluster │
│ │ Cilium │ │
│ Control Plane │ Cluster │ Control Plane │
│ Worker Nodes │ Mesh │ Worker Nodes │
└─────────────────┘ └─────────────────┘
- Multiple KubeAid clusters deployed (see Cloud Providers)
- Network connectivity between clusters (routable IPs or VPN)
- Cilium installed on all clusters (included by default)
- Compatible Cilium versions across clusters
- Unique cluster names in the mesh
- Enable Cluster Mesh:
cilium clustermesh enable --context <cluster1-context>
cilium clustermesh enable --context <cluster2-context>- Connect clusters:
cilium clustermesh connect \
--context <cluster1-context> \
--destination-context <cluster2-context>- Verify connectivity:
cilium clustermesh status --context <cluster1-context>For detailed configuration, see the Cilium Cluster Mesh documentation.
Note: This is different from Cilium Cluster Mesh.
Hetzner's built-in hybrid mode creates a single cluster with mixed node types:
- Control plane in HCloud (VMs)
- Worker nodes in HCloud and/or Bare Metal
See Cloud Providers - Hetzner Hybrid for setup instructions.
- Cloud Providers - Individual cloud provider setup
- Bare Metal - On-premises clusters