Gateway API v1.4.1
Release Notes
Warning: Regarding the Experimental CRDs - please note that the experimental CRDs for this release are too large for a standard kubectl apply. You may receive an error like metadata.annotations: Too long: may not be more than 262144 bytes. To work around this please use kubectl apply --server-side -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.4.0/experimental-install.yaml. We're looking into ways to reduce the size for future releases to avoid this.
Note: The installation YAML originally published with this release on 2025-12-04 mistakenly included changes from PR 3823 in the Standard channel, and from PRs 3774, 3823, and 4158 in the Experimental channel. After discussion among the Gateway API maintainers, we decided that the changes were minor enough that it was safe to modify the YAML in-place, which we did on 2026-02-10. Apologies for the confusion!
Changes Since v1.4.0
BackendTLSPolicy
- BackendTLSPolicy supports only a single
targetRefper policy while Gateway API works through edge cases around representing the status of multipletargetRefsin a single policy. This restriction is expected to be lifted in a future release. (#4316, #4298) - SAN validation in BackendTLSPolicy is correctly marked as standard. (#4194)
- BackendTLSPolicy
statusis correctly marked as a subresource. (#4245)
Conformance
- Conformance tests for mesh routing with weights have been made faster. (#4315)
- BackendTLSPolicy conformance tests are included in the GATEWAY-HTTP profile. (#4223)
Thanks to
Ciara Stacke, Lior Lieberman, Nick Young, Norwin Schnyder, Ricardo Pchevuzinske Katz, and zirain
Full Changelog
Full Changelog: https://github.com/kubernetes-sigs/gateway-api/compare/v1.4.0...v1.4.1