Gateway API v0.6.2
Release Notes
API versions: v1beta1, v1alpha2
This is a patch release that predominantly includes updated conformance tests for implementations to implement.
For all major changes since the v0.5.x release series, please see the
v0.6.0 release notes.
Maintenance
- As per changes in upstream to container image registries we replaced all usage of the k8s.gcr.io registry with registry.k8s.io. (#1736, @shaneutt)
Bug Fixes
- Fix invalid HTTP redirect/rewrite examples. (#1787, @Xunzhuo)
Conformance Test Updates
- The
HTTPRouteInvalidCrossNamespaceParentRefconformance test now checks for theNotAllowedByListenersreason on theHTTPRoute'sAccepted: falsecondition to better indicate why the route was note accepted. (#1714, @skriss) - A conformance test was added for
HTTPRouteto cover the behavior of a non-matchingSectionNamesimilar to what was already present forListenerPort. (#1719, @zaunist) - Fixed an issue where tests may fail erroneously on the removal of resources that are already removed. (#1745, @mlavacca)
- Logging in conformance utilities related to resource's
ObservedGenerationhas been improved to emit the `ObservedGenerations that are found for the purpose of making it easier to debug test failures and be more verbose about the objects in question. (#1761, @briantkennedy) (#1763, @briantkennedy) - Patch instead of update in some places in conformance tests to reduce noise in logs. (#1760, @michaelbeaumont)
- Added
AttachedRoutestesting to conformance tests. (#1624, @ChaningHwang) - The conformance tests always check that the HTTPRoute ResolvedRefs condition is enforced, even when the status is true. (#1668, @mlavacca)