Kubernetes Ingress & Gateway API Updates, with Lior Lieberman
Mar 11, 2025
auto_awesome
Lior Lieberman, a software engineer lead at Google Cloud, is a key player in Kubernetes networking and the Gateway API. He discusses the challenges and evolution of the Gateway API as a significant upgrade from the Ingress API. Lior emphasizes the API's advanced routing features and production readiness, debunking myths about its predecessor. He also highlights the importance of community collaboration in navigating these transitions and the future of Kubernetes extensibility, showcasing the impact of such innovations on service mesh integration.
Kubernetes 1.29 introduces a new NF tables mode for Kube Proxy, addressing performance issues with the previous IP tables mode.
The Gateway API offers enhanced flexibility and a robust permission model, facilitating a smoother transition from the traditional Ingress API.
Deep dives
Introduction of New Features in Kubernetes
Kubernetes 1.29 introduces a new NF tables mode for Kube Proxy, which aims to resolve long-standing performance issues associated with the IP tables mode. Currently in beta, this mode is anticipated to become generally available in version 1.33. Users running a newer Linux kernel are encouraged to test this feature and provide feedback on its performance improvements. Moreover, the CNCF has welcomed KubeScape as a new incubating project, which focuses on comprehensive security coverage throughout the development and deployment lifecycle for Kubernetes applications.
Insights into Gateway API Development
The conversation introduces Lior Liberman, a prominent contributor to the Gateway API and maintainer of Ingress to Gateway, who shares his experiences with Kubernetes networking. Lior emphasizes the challenges he faced when initially engaging with Kubernetes, portraying it as complicated and frustrating, especially concerning debugging and service rollout processes. His transition to using Kubernetes revealed its potential to streamline operations within a growing development environment, which led to a community-driven approach to resolve issues via platforms like GitHub and Slack. This foundational support within the community illustrates the collaborative spirit that drives advancements like the Gateway API.
Limitations of Ingress and Advancements with Gateway API
The limitations of the traditional Ingress API are noted, particularly its simplicity which often leads to complex implementations through custom annotations, making configurations non-portable across different environments. The Gateway API was designed to overcome these shortcomings by allowing protocol diversity and providing a more sophisticated permission model suited for different user personas. Its development has been oriented towards extensibility, ensuring that various pieces of functionality can grow together without being tightly bound to the core Kubernetes codebase. This flexibility and modularity present Gateway API as a more robust solution to meet modern networking needs.
Migration Path from Ingress to Gateway API
As organizations look to migrate from the Ingress API to the Gateway API, a new tool called Ingress to Gateway has been introduced to facilitate this transition. This tool aims to provide a foundational starting point for users, converting existing Ingress configurations to the equivalent Gateway API resources while highlighting unsupported features. The maintainers are keen on community feedback to continuously improve this migration process, indicating a future where Gateway API becomes the standard for new Kubernetes applications. The ease of migrating to Gateway is underscored by its increasing adoption rates, with expectations that it will become the default choice for Kubernetes networking going forward.
Lior Lieberman is a software engineer lead at Google Cloud focusing on GCE, Kubernetes, and Service Mesh. He is a leading contributor to Gateway API and the maintainer of Ingress2gateway.
Do you have something cool to share? Some questions? Let us know: