If you are going to be running multiple clusters for dev and organizational reasons, it’s important to understand your requirements and decide whether you want to connect these in a multicluster environment and, if so, to understand various approaches and associated tradeoffs with each option.
Kubernetes has become the container orchestration standard, and many organizations are currently running multiples clusters. But while communication issues within clusters are largely solved, communication across clusters is still a major challenge for most organizations.
Service mesh helps to address multicluster challenges. Start by identifying what you want, then shift to how to get it. We recommend understanding your specific communication use case, identifying your goals, then creating an implementation plan.
Multicluster offers a number of benefits:
- Single pane of glass
- Unified trust domain
- Independent fault domains
- Intercluster traffic
- Heterogenous/non-flat network
Which can be achieved with various approaches:
- Independent clusters
- Common management
- Cluster-aware service routing through gateways
- Flat network
- Split-horizon Endpoints Discovery Service (EDS)
If you have decided to multicluster, your next move is deciding the best implementation method and approach for your organization. A service mesh like Istio can help, and when used properly can make multicluster communication painless.
Read the full article here on InfoQ’s site.