Gateway API is a collection of resources that focus on network traffic of Kubernetes Services. It provides a powerful, extensible, and role-oriented Service network model.
Introduction
Gateway API provides the following benefits:
Role-oriented: Gateway API keeps resource abstractions consistent with organizational roles that use and configure Kubernetes.
Portable: Same as the correlation between Ingresses and the Ingress controller, Gateway API also supports a variety of implementations.
Expressive: Gateway API supports advanced traffic processing capabilities through an expressive structure, such as canary release and weighted release. With these capabilities, Ingresses no longer need to rely on annotations to handle traffic.
Extensible: Gateway API allows for custom resources to be linked at various layers of the API. This makes granular customization possible at the appropriate places within the API structure.
Usage notes
You can choose an implementation for Gateway API from the open source community and then use Gateway API to configure the Service network. For more information, see Implementations.
Release notes
June 2025
Version | Release date | Description | Impact |
v1.3.0 | 2025-06-05 | Note This version supports only ACS clusters that run Kubernetes 1.32 and later.
| No impact on workloads. |