From Zero to Cluster Mesh: Installing and Configuring Cilium CNI on Kubernetes

Welcome to this comprehensive tutorial on how to install and configure the Cilium CNI (Container Network Interface) and enable its advanced cluster mesh feature across Kubernetes clusters in different availability zones!
What You Will Learn:
🛠 How to install the Cilium CNI
🤝 Enabling cluster mesh between two Kubernetes clusters
🌍 Setting up clusters in different availability zones
📊 Monitoring and troubleshooting
What is Cilium CNI?
Cilium is an open-source networking and security project that provides a highly efficient CNI Plugin for Kubernetes. Leveraging eBPF (extended Berkeley Packet Filter), Cilium offers robust networking capabilities, advanced load balancing, and enhanced security features for microservices.
What is Cluster Mesh?
Cluster Mesh is an incredible feature provided by Cilium that allows seamless connectivity between multiple Kubernetes clusters. With cluster mesh, you can extend your network policies, load balancing, and other networking features across different clusters, even if they are located in separate availability zones.
📚 Resources:
Cilium CNI Cluster Mesh Documentation - docs.cilium.io/en/latest/netw...
Cilium CNI Cluster Mesh Deep Dive (2019) - cilium.io/blog/2019/03/12/clu...

[@ManiBalajiC]

so Cilium provide both cluster mesh and service mesh for the pods ? , does isito do the same ?

[@BoyanOrion]

Thank you for the excellent video and demonstration of Cillium!

[@virtualelephant]

Glad you enjoyed it!

[@SuperDavinci123]

Hi Chris thanks for the amazing stuff, can you also make a video on how to add new worker node to existing cluster with cilium

[@virtualelephant]

I will add it to my queue

[@tonylagumen2810]

Hi there! Could you incorporate an additional section into this tutorial that delves deeper into the step-by-step process of creating these two clusters using kubeadm? I'm keen on understanding the setup of each cluster, including the assignment of unique cluster names, podSubnets and kubectl configuration context for these clusters. Thank you -

[@Grg456ful]

This brings up some questions. Did you install both clusters with seperate contexts on each site? how is az1-cluster on site 1 finding az2-cluster on site2 by L3 routing? did you use the same Pod Networks for the clusters on each site?

[@zozo6015]

he said that the two clusters should have different pod networks.