Reducing Kubernetes tool sprawl: Tietoevry uses Cilium and Hubble
Tietoevry uses Isovalent Enterprise for Cilium to have advanced network policies (DNS!), reduce tool sprawl, and get the necessary insights to monitor the various SLAs.
Video
Tietoevry: More than just a CNI - Cilium and Hubble as the cloud native network stack
In this video, learn how Cilium and Hubble can help IT service providers with many teams and clusters to standardize on a powerful, fully cloud-native network stack.
Watch the recording now!
What you will learn:
Join David and Endre from Tietoevry Industry in this on-demand webinar to see how Isovalent Enterprise for Cilium made daily Kubernetes operations this much easier – especially in the morning, before the first coffee.
There are tons of CNIs. But when you want to go into production, you need something more, with a roadmap, a real plan of the future, and the right feature set to standardize upon.
At Tietoevry Industry, an IT service provider with 24,000 employees and an annual turnover of EUR 3 billion, a platform team that runs more than 30 Kubernetes clusters with hundreds of applications identified Isovalent Enterprise for Cilium as the network stack for their clusters.
Tune in to learn from David and Endre how Isovalent Enterprise for Cilium enabled them to overcome tool sprawl, eased the challenges of app modernization, helped with migrating apps to the cloud, and supported the integration with the wider environment.
You will learn:
- … how deploying Isovalent Enterprise for Cilium reduced tool sprawl.
- … how advanced network policies with FQDNs/DNS make the network integration safer.
- … how Hubble can help establish Zero Trust principles.
- … how deep observability like TCP latencies help with troubleshooting applications.
- … how observability can be provided in a self-service fashion to application owners, freeing the SREs from troubleshooting burden.
- … how migration and modernization of apps is much easier with Isovalent Enterprise for Cilium.
- … how to achieve consistent cloud native networking – regardless of the public or private cloud.
- … how to use Isovalent Enterprise for Cilium to eliminate fingerpointing and improve SLA reporting.
- … how to enhance observability of your applications running on Kubernetes by leveraging Hubble, Grafana for better tracing and monitoring.
- … and why the network policy editor is crucial when you have to troubleshoot network policies before the first coffee in the morning. ☕
Speakers
Do you have any questions?Contact us
Related Content
Avoiding cloud vendor lock-in with Kubernetes and Cilium – Form3
To avoid cloud vendor lock-in, Form3 chose Cilium and Kubernetes.
Migrating from Flannel
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.