 |
VOOZH | about |
|
VOOZH | about |
We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.
Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups.
Follow TNS on your favorite social media networks.
Become a TNS follower on LinkedIn.
Check out the latest featured and trending stories while you wait for your first TNS newsletter.
Kubernetes network administrators at KubeCon + CloudNativeCon EU this week in London should drop by the Solo.io booth #S150 to learn about an open source Kubernetes API Gateway implementation, called kgateway, that could ease the management of moving traffic to and from clusters.
Built on top of Envoy proxy and the Kubernetes Gateway API, the open source kgateway is a Kubernetes-native ingress controller and next-generation API gateway.
The gateway was built by cloud native connectivity company Solo.io, and went under the name Gloo Gateway.
At last year’s KubeCon +_ CloudNativeCon North America 2024, the company announced that it would be donating the software to the Cloud Native Computing Foundation (CNCF), changing the software’s name to kgateway in the process.
In March, CNCF accepted kgateway as a sandbox project, the entry point for early stage cloud native software projects.
By moving to a vendor neutral governance, users, and contributors do not have to worry about the software being donated by a single vendor.
The Gloo open source repository will be deprecated over time.
In 2023, the Kubernetes Gateway API achieved version 1.0 production release. The API Gateway is a specification of how to control the traffic in and out of Kubernetes clusters, as well as how to shuttle traffic internally between pods.
Kgateway is a fully conformant implementation of the Kubernetes Gateway API. The API is a specification for how to route traffic, both on the “layer 4” control plane and the “layer 7” data plane.
It is actually an interface to the Envoy proxy, which manages L7 data traffic for a Kubernetes cluster. Programming Envoy directly, however, is difficult. What kgateway does is provide a more intuitive interface to program network traffic for end users, which could include infrastructure providers, cluster operators, and application developers.
Kgateway reads the Gateway API rules set by the administrators and then executes them using Envoy.
“Kgateway supports the Kubernetes Gateway API so that user can use this intuitive user interface that’s composed of the Gateway HTTP route,” said Lin Sun, Solo.io’s director of open source, in an interview with TNS.
According to Sun, the goal for kgateway is to be the default gateway for all-direction Kubernetes traffic (both north-south and east-west internal traffic).
The project is working on expanding the capabilities of the software as well.
For instance, kgateway is positioning itself as an “AI Gateway” to address the unique security and management challenges of integrating applications with LLMs.
Project developers are on the Kubernetes Network Special Interest Group, which is working on a new project, the “Gateway API Inference extension.”
This extension will give Kubernetes inference-specific routing capabilities, allowing K8s deployments to work more easily with generative AI-driven workloads through routing, secret management, backup LLMs and other capabilities.
Kgateway is also being tightly integrated with the Istio Ambient mesh, which seeks to do away with sidecars entirely. For Istio in Ambient Mode, kgateway can function as a waypoint proxy, providing advanced L7 features not available in Istio itself, such as request transformation, retries, traffic control for AI workloads.
Sun explains further here:
