Gateway API: Bridging the Gap from Ingress to the Future - Panel

A panel of experts discusses recent improvements and upcoming features in the Kubernetes Gateway API.

Don't miss out! Join us at our next KubeCon + CloudNativeCon events in Mumbai, India (18-19 June, 2026), Yokohama, Japan (29-30 July, 2026), and Shanghai, China (8-9 September, 2026). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at kubecon.io Gateway API: Bridging the Gap from Ingress to the Future - Nick Young & James Strong, Isovalent at Cisco; Katarzyna Łach & Rostislav Bobrovsky, Google; Norwin Schnyder, Airlock Gateway API continues to mature into a core part of the toolkit for Cloud Native networking. But, since the last Gateway API update, some big changes have happened. This session goes through some of the recent improvements that have happened in Gateway API in the last six months, along with laying out some of the upcoming features. In particular, with the archival of ingress-nginx coming up, many more Ingress users have been looking at Gateway API, and the community has been hard at work trying to smooth out friction points for those users, especially with helping with migration (using the ingress2gateway tool), improving integrations with tools like cert-manager and external-dns, and making improvements to TLS handling. In particular, the new ListenerSet resource moving to Standard is intended to help Ingress users have an experience more like what they are used to, while keeping some of the enhanced security features that Gateway API brings.