Request a demo
See Isovalent Enterprise for Cilium in action
Request a demoMigrating to Cilium from another CNI is a very common task. But how do we minimize the impact during the migration? How do we ensure pods on the legacy CNI can still communicate to Cilium-managed during pods during the migration? How do we execute the migration safely, while avoiding a overly complex approach or using a separate tool such as Multus?
With the use of the new Cilium CRD CiliumNodeConfig
, running clusters can be migrated on a node-by-node basis, without disrupting existing traffic or requiring a complete cluster outage or rebuild.
In this lab, you will migrate your cluster from an existing CNI to Cilium. While we use Flannel in this simple lab, you can leverage the same approach for other CNIs.
Explore the lab's environment
Let's prepare our cluster for the migration to Cilium.
Let's migrate from Flannel to Cilium.
Let's perform these steps once the cluster is fully migrated.
eBPF-based enforcement, visibility & forensics
eBPF-based networking & load-balancing
eBPF-based network & application visibility
See Isovalent Enterprise for Cilium in action
Request a demoJoin an “ask me anything” session with Thomas Graf, creator of Cilium, co-founder of Isovalent
Add to calendarLearn about Isovalent Enterprise for Cilium with our interactive labs
Start hands-on labSoftware for providing, securing and observing network connectivity
Revolutionary technology with origins in the Linux kernel
We look forward to engaging with you around all things Cilium and eBPF
Get in touch