Exiting Ingress With the Gateway API

The presentation discusses the advantages of using Gateway API over Ingress API in Kubernetes for advanced use cases such as traffic splitting and secure certificate management.

• Gateway API is more expressive, extensible, and portable than Ingress API
• Gateway API offers easier and safer ways to implement advanced use cases such as traffic splitting and secure certificate management
• Automated transition processes for traffic shifting may require additional tools such as Flagger or Argo

The presentation highlights the creative implementations of Ingress API for traffic splitting and secure certificate management, but also emphasizes the limitations of Ingress API in terms of new feature development. Gateway API offers a more comprehensive solution for advanced use cases and is designed to be an extension of Kubernetes rather than a core component. The presentation also suggests that automated transition processes for traffic shifting may require additional tools such as Flagger or Argo.

Are you currently using Ingress but curious about what Gateway API is? Wondering if you should switch to Gateway API or how that would even work? This is the talk for you. The development of Gateway API has unlocked a wide set of new capabilities within Kubernetes, but it can also be overwhelming to understand the full scope of it. In this talk, Rob and Shane will answer some of the most common questions they get as Gateway API maintainers, including what you gain over using the Ingress API. They’ll walk through a step-by-step demo of what it takes to get started with Gateway API. This demo will show you how to migrate from Ingress to Gateway API and showcase some of the newest features in Gateway API, including traffic splitting between backends in different namespaces.