Were you unable to attend Transform 2022? Check out all of the summit sessions in our on-demand library now! Watch here.
There’s no question that Kubernetes has become the new enterprise standard when it comes to building and operating modern applications.
According to the Cloud Native Computing Foundation’s (CNCF) annual survey, 96% of organizations are either using or evaluating the container orchestration system.
As such, today’s enterprises and telcos are past the Day 1 phase of Kubernetes, said Dan Wendlandt, CEO of Isovalent.
And, as they grow into the Day 2 phase, organizations are learning that Kubernetes does not, on its own, provide a networking layer with the security, observability, reliability and performance required of more mission-critical workloads, he pointed out.
MetaBeat will bring together thought leaders to give guidance on how metaverse technology will transform the way all industries communicate and do business on October 4 in San Francisco, CA.
This has pushed demand for open-source technologies — including Cilium and eBPF. To help meet these ever-increasing needs, Isovalent today announced that it has closed a $40M series B funding round. The company created the Cilium project and provides Isovalent Cilium Enterprise, technologies both enabled by the new Linux kernel technology eBPF.
“eBPF is the single most interesting thing to happen in Linux in the past 10 or even 20 years,” said Wendlandt. And, while Isovalent started as an “all-in” bet on the technology and Kubernetes, “we are still in the early days of seeing all the ways in which Cilium and eBPF will transform the modern infrastructure layer.”
Kubernetes Day 2 challenges
“Which Kubernetes distro do I run?” “How do I migrate my initial applications onto Kubernetes?” Those are common Day 1 questions. But now that businesses have “figured out” how to run Kubernetes itself, they are tackling Day 2 challenges such as the following:
“How do I troubleshoot connectivity failures or poor performance between two services running in Kubernetes?”“How does my security team perform an incident investigation in my Kubernetes environment?”Not only does Kubernetes not have built-in capabilities to tackle these problems, but traditional network infrastructure devices — firewalls, network load-balancers, network monitoring devices — are also limited in closing gaps, said Wendlandt. Such devices then become bottlenecks, given the explosion of API-communication between modern applications. Similarl …