Gateway API v1.0: A Milestone for Kubernetes Routing

We are excited to announce the release of Gateway API v1.0 on behalf of the Kubernetes SIG Network! This release marks a significant milestone for the project. Several core APIs have reached “generally available” (GA) status, while other major features have been included in the experimental channel.

What’s New?

Graduation to v1

This release includes the graduation of Gateway, GatewayClass, and HTTPRoute to v1. This means they are now generally available (GA). This API version indicates a high level of confidence in the API surface and offers guarantees for backward compatibility. Note that the version of these APIs included in the standard channel is now considered stable, but this does not mean they are complete. These APIs will continue to receive new features through the experimental channel as they meet the criteria for graduation. For more information, see the Gateway API Versioning Policy.

Logo

The Gateway API now has a logo! This logo was designed through a collaborative process and is intended to represent the idea that it is a collection of Kubernetes APIs for traffic routing in both north-south and east-west directions:

CEL Validation

Historically, the Gateway API bundled a validating webhook as part of the API installation. As of v1.0, installing the webhook is optional and only recommended for Kubernetes 1.24. The Gateway API now includes CEL validation rules as part of the CRDs. This new form of validation is supported in Kubernetes 1.25+, which is why the validating webhook is no longer required in most installations.

Standard Channel

This release primarily focused on ensuring that the existing beta APIs are well-defined and stable enough to reach GA. This led to a variety of specification clarifications as well as some status improvements to enhance the user experience when interacting with the Gateway API.

Experimental Channel

Most of the changes included in this release were confined to the experimental channel. These include HTTPRoute timeouts, TLS configuration from gateways to backends, WebSocket support, gateway infrastructure labels, and more. Stay tuned for a follow-up article that will cover each of these new features in detail.

Everything Else

For a complete list of changes included in this release, please take a look at the v1.0.0 release notes.

How Did We Get Here?

The idea of the Gateway API was proposed 4 years ago at KubeCon in San Diego as the next generation of the Ingress API. Since then, an incredible community has formed, working on what has likely become the most collaborative API in Kubernetes history. So far, over 170 people have contributed to this API, and that number continues to grow.

A special thanks goes to the 20+ community members who were willing to take on an official role in the project and invest some time in reviews as well as share the responsibility for maintaining the project!

We would especially like to highlight the emeritus maintainers who played a crucial role in the early development of this project:

• Bowei Du
• Daneyon Hansen
• Harry Bagdi

With the new features of Gateway API v1.0, developers and DevOps teams have an excellent opportunity to make their Kubernetes applications more efficient. ayedo is excited to be part of this exciting development as a Kubernetes partner and is happy to support you in leveraging the benefits of this new API!

Source: Kubernetes Blog