Request a demo
See Isovalent Cilium Enterprise in action
Request a demoKubernetes changes the way we think about networking. In an ideal Kubernetes world, the network would be entirely flat and all routing and security between the applications would be controlled by the Pod network, using Network Policies.
In many Enterprise environments, though, the applications hosted on Kubernetes need to communicate with workloads living outside the Kubernetes cluster, which are subject to connectivity constraints and security enforcement. Because of the nature of these networks, traditional firewalling usually relies on static IP addresses (or at least IP ranges). This can make it difficult to integrate a Kubernetes cluster, which has a varying —and at times dynamic— number of nodes into such a network.
Cilium’s Egress Gateway feature changes this, by allowing you to specify which nodes should be used by a pod in order to reach the outside world.
Set up the lab's environment
Let's deploy an echo server outside of the cluster!
Let's add an Egress Gateway Policy to route to the echo server!
Verify your learnings from this lab!
eBPF-based enforcement, visibility & forensics
eBPF-based networking & load-balancing
eBPF-based network & application visibility
See Isovalent Cilium Enterprise 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 Cilium Enterprise 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