Kubernetes multi-cluster implementation in under 10 minutes

<blockquote> You should not mix the Cilium CLI helm mode to enable ClusterMesh or connect clusters configured by the Cilium CLI — they are operating in classic mode — as the two modes are not compatible with each other. We are not going to use Cilium CLI to install Cilium, but Helm instead. Cilium CLI would come handy afterwards, when we’d need to run some connectivity tests. </blockquote> <h1>What is Cilium ClusterMesh?</h1> ClusterMesh is Cilium’s multi-cluster implementation. It extends the networking datapath across multiple Kubernetes clusters. It allows endpoints that live in different connected clusters to communicate and on the same time it provides full policy enforcement. ClusterMesh provides (excerpt taken from the official article “<a href="https://cilium.io/blog/2019/03/12/clustermesh/" rel="noopener ugc nofollow" target="_blank">Deep Dive into Cilium Multi-cluster</a>”): <ul> <li>Pod IP routing across multiple Kubernetes clusters at native performance via tunneling or direct-routing without requiring any gateways or proxies.</li> <li>Transparent service discovery with standard Kubernetes services and <code>coredns/kube-dns</code>.</li> <li>Network policy enforcement spanning multiple clusters. Policies can be specified as Kubernetes <code>NetworkPolicy</code> resource or the extended <code>CiliumNetworkPolicy</code> CRD.</li> <li>Transparent encryption for all communication between nodes in the local cluster as well as across cluster boundaries.</li> </ul> <a href="https://akyriako.medium.com/kubernetes-multi-cluster-implementation-in-under-10-minutes-2927952fb84c">Read More</a>