Webinar
Stop Hoarding Networking Tools: Declutter Your Cluster with the Isovalent Platform
On-Demand
Less Overhead, More Velocity
Kubernetes engineers love nothing more than collecting tools to run, connect, and observe applications in their clusters. But what starts as innovation can quickly turn into overload: service mesh, ingress, load balancer, multi-cluster management, observability, egress - the list grows fast, and your cluster pays the price.
It’s time to simplify! Cilium is the de facto Kubernetes networking platform that replaces multiple tools with one powerful solution.
In this webinar, you'll get practical tips on how to:
- Clean up your cluster
- Reduce tool sprawl
- Build a leaner, more efficient environment that’s easier to manage
This session is perfect for anyone looking to simplify their Kubernetes setup and bring order to the chaos.
Can't make it to the live session? Register anyway and we'll send you the recording!
Kubernetes makes development powerful, but when every problem adds a new tool, clusters get bloated fast. Join to learn how the Isovalent Enterprise Platform helps you streamline your stack and regain control.
Nico Vibert, Principal Technical Marketing Engineer
Nico Vibert is a Principal Technical Marketing Engineer at Isovalent, the company behind the open-source cloud-native solution Cilium. Prior to joining Isovalent, Nico worked in many different roles - operations and support, design and architecture, and technical pre-sales - at companies such as HashiCorp, VMware, and Cisco. In his current role, Nico focuses primarily on creating content to make networking a more approachable field and regularly speaks at events like KubeCon and Cisco Live. Nico has held over 15 networking certifications, including the Cisco Certified Internetwork Expert CCIE (# 22990). Nico is the co-author of the "Cilium: Up and Running" O'Reilly book and is the Lead Subject Matter Expert on the Cilium Certified Associate (CCA) certification.
Dan Finneran, Principal Community Advocate
Dan Finneran is a Principle Community Advocate at Isovalent. His journey to today has included bare-metal, jails, zones, vms and containers where he is currently enjoying the fast paced ride in the cloud native space. He also created & maintains a popular Open-Source load-balancer for Kubernetes and contributes to upstream Kubernetes. He's also been fortunate to present at events ranging from the British computing society, HPE Technical solutions summit to DockerCon and KubeCon amongst others.
Related Content
Discover more from Isovalent
Tutorial: How to Migrate to Cilium
In this series, learn how you can migrate to Cilium! First, let's learn about the migration approach and walk through an example migrating from Flannel to Cilium.
Fast-Tracking Your Migration From Ingress to Gateway API
Struggling with Kubernetes Ingress limitations? Discover how to easily migrate to Cilium’s Gateway API implementation.
Migrating from Flannel
Migrating Lab
Migrating 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.
Note that this feature is still beta and we expect further tooling and automation to be developed to support large cluster migrations.