← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Cilium 1.20 Expands Kubernetes Gateway API Support and Opens eBPF Datapath

🔄 Updated 17d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Cilium 1.20 adds ExternalAuth, ListenerSets, TCPRoute, UDPRoute to Gateway API.
  • ExternalAuth allows external authorization services for HTTP requests.
  • TCPRoute and UDPRoute support Layer 4 traffic without LoadBalancer/NodePort.
  • eBPF datapath now supports third-party plugins for custom networking.

Expanded Gateway API Capabilities

Cilium 1.20 introduces significant advancements in its Kubernetes Gateway API support, moving from version 1.4 to 1.6. Key additions include ExternalAuth, ListenerSets, CORS filtering, TCPRoute, and UDPRoute. These features extend traffic management capabilities to include HTTP authentication and non-HTTP services like databases and DNS, integrating them under the standard Kubernetes API used for web and gRPC traffic.

Enhanced Authorization and Layer 4 Routing

The ExternalAuth feature enables HTTPRoute to consult an external authorization service before forwarding requests to an application. This allows for conditional request handling, such as forwarding, redirecting to a login page, or rejection, and can pass identity headers. TCPRoute and UDPRoute eliminate the need for LoadBalancer or NodePort Services for plain Layer 4 traffic, simplifying network configurations for these types of services.

Improved Multi-Team Gateway Management

ListenerSets address ownership challenges in multi-team environments. Application teams can now add listeners from their own namespaces, while platform teams maintain control over the shared Gateway and define which namespaces can extend it. This change removes a common bottleneck where central platform teams were required for every new hostname or port configuration.

Open eBPF Datapath for Customization

A major change in Cilium 1.20 is the opening of its eBPF datapath to third-party plugins. Previously, cloud providers needing custom instrumentation or networking behaviors had to contribute changes upstream or maintain their own forks. Now, plugins can run separately, offering greater flexibility and reducing the overhead for custom network integrations.

Alignment with Kubernetes Networking Trends

These updates align with broader trends in Kubernetes networking, where the Gateway API is increasingly recommended as organizations transition away from older controllers like Ingress NGINX. Cilium's implementation is notable for providing CNI, service networking, and gateway functions within a single project, offering a unified solution.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Primary sources

GitHub cilium/cilium

Reporting from

Cilium 1.20 has been released, enhancing Kubernetes Gateway API support with features like ExternalAuth, ListenerSets, TCPRoute, and UDPRoute. This update allows for broader traffic management, including non-HTTP services and external authorization, and opens the eBPF datapath for third-party plugins, reducing the need for upstream contributions or forks for custom networking behaviors.