Releases · kubernetes-sigs/gateway-api

08 Feb 19:22

shaneutt

v0.6.1

e5170d1

v0.6.1

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.

Bug Fixes

Our regex for validating path characters was updated to accurately identify
"p-chars" as per RFC-3986.
(#1644, @jackstine)
An erroneous "namespace" field was present in our webhook ClusterRoleBindings
and has been removed.
(#1684, @tao12345666333)

New Features

Conditions for Policies have been added to the Golang library, enabling
Go-based implementations to re-use those for their downstream Policies.
(#1682, @mmamczur)

Conformance Test Updates

Added conformance tests for checking Port, Scheme and Path to the extended and
experimental features.
(#1611, @LiorLieberman)
Added conformance tests for HTTP rewrite
(#1622, #1628, @LiorLieberman)
Added more conformance tests for path matching to catch known edge cases.
(#1627, @sunjayBhatia)
Added some initial conformance tests for TLSRoute passthrough.
(#1579, @candita)
Added conformance tests that exercise NotAllowedByListeners reason.
(#1669, @mlavacca)
Loosen the Accepted check in GatewayClass observed generation tests to
provide a more realistic test for implementations.
(#1655, @arkodg)
A "SkipTests" field has been added to accomodate implementations in
running subsets of the tests as needed, this can be particularly helpful
for new implementations that want to add conformance iteratively.
(#1578, @mlavacca)
Fixed a broken test for GRPCRoute that caused an erronous failure.
(#1692, @arkodg)
Added "all-features" flag to conformance test to enable all supported
features on test runs.
(#1642, @gyohuangxin)
Fixed usage of net/http default client in conformance test suite
(#1617, @howardjohn)
Fixed missing reference to NoMatchingParent in godoc
(#1671, @mlavacca)

Full Changelog: v0.6.0...v0.6.1

Contributors

howardjohn, jackstine, and 8 other contributors

Assets 4

0 Join discussion

21 Dec 13:14

shaneutt

v0.6.0

6c222d3

v0.6.0

API versions: v1beta1, v1alpha2

Major Changes

ReferenceGrant moves to `v1beta1`, ReferencePolicy removed

With more implementations now supporting ReferenceGrant (and more conformance coverage of the resource), we've moved ReferenceGrant to v1beta1 in this release. Note that moving to beta also moves the object to the Standard channel (it was Experimental previously).

We've also removed the already-deprecated ReferencePolicy resource, so please move over to the shiny new ReferenceGrant, which has all the same features.

Promotes ReferenceGrant to the v1beta1 API and the standard release channel
(#1455, @nathancoleman)
ReferencePolicy has been removed from the API in favor of ReferenceGrant.
(#1406, @robscott)

Introduce GRPCRoute

The GRPCRoute resource has been introduced in order to simplify the routing of GRPC requests.
Its design is described in GEP-1016.
As it is a new resource, it is introduced in the experimental channel.

Thanks to @gnossen for pushing this ahead.

Introduce GRPCRoute resource. (#1115, @gnossen)

Status updates

As described in GEP-1364, status conditions have been updated within the Gateway resource to make it more consistent with the rest of the API. These changes, along with some other status changes, are detailed below.

Gateway:

New Accepted and Programmed conditions introduced.
Scheduled condition deprecated.
Core Conditions now Accepted and Programmed.
Moves to Extended: Ready.

Gateway Listener:

New Accepted and Programmed conditions introduced.
Detached condition deprecated.
Core Conditions now Accepted, Programmed, ResolvedRefs, and Conflicted.
Moves to Extended: Ready.

All Resources:

The Accepted Condition now has a Pending reason, which is the default until
the condition is updated by a controller.

Route resources:

The Accepted Condition now has a NoMatchingParent reason, to be set on routes
when no matching parent can be found.

The purpose of these changes is to make the status flows more consistent across objects, and to provide a clear pattern for new objects as we evolve the API.

Note: This change will require updates for implementations to be able to pass conformance tests. Implementations may choose to publish both new and old conditions, or only new conditions.

Adds Accepted and deprecates Detached Listener conditions and reasons (#1446, @mikemorris)
Adds Accepted and deprecates Scheduled Gateway conditions and reasons (#1447, @mikemorris)
Adds Pending reason for use with all Accepted conditions throughout the API (#1453, @youngnick)
Adds Programmed Gateway and Listener conditions, moves Ready to extended
conformance (#1499, @LCaparelli)
Add RouteReasonNoMatchingParent reason for Accepted condition. (#1516, @pmalek)

Other Changes by type

Deprecations

GatewayClass, Gateway, and HTTPRoute are now only supported with the v1beta1
version of the API. The v1alpha2 API versions of these resources will be fully
removed in a future release. Additionally, v1alpha2 is marked as deprecated
everywhere. (#1348 and #1405, @robscott)

API Changes

A new field responseHeaderModifier is added to .spec.rules.filters, which
allows for modification of HTTP response headers (#1373, @aryan9600)
Display the Programmed condition instead of the Ready condition in the output
HTTPRoute: Validating webhook now ensures that Exact and Prefix path match
values can now only include valid path values per RFC-3986. (RegularExpression
path matches are not affected by this change). (#1599, @robscott)
RegularExpression type selectors have been clarified to all be
ImplementationSpecific conformance. (#1604, @youngnick)

Documentation

Clarify that BackendObjectReference's Port field specifies a service port, not
a target port, for Kubernetes Service backends. (#1332, @Miciah)
HTTPRequestHeaderFilter and HTTPResponseHeaderFilter forbid configuring
multiple actions for the same header. (#1497, @rainest)
Changes "custom" conformance level to "implementation-specific" (#1436,
@LCaparelli)
Clarification that changes to ReferenceGrants MUST be reconciled (#1429,
@robscott)

Conformance Tests

ExemptFeatures have been merged into SupportedFeatures providing implementations
a uniform way to specify the features they support.
(#1507, @robscott) (#1394, @gyohuangxin)
To be conformant with the API, if there is no ReferenceGrant that grants a
listener to reference a secret in another namespace, the
ListenerConditionReason for the condition ResolvedRefs must be set to
RefNotPermitted instead of InvalidCertificateRef. (#1305, @mlavacca)
A new test has been added to cover HTTP Redirects (#1556, @LiorLieberman)
Fix Gateway reference in HTTPRouteInvalidParentRefNotMatchingListenerPort
(#1591, @sayboras)

Build Changes

We now provide a multi-arch
image including new support for arm64 in addition to amd64 for our
validating webhook.
(#627, @wilsonwu & @Xunzhuo)

Developer Notes

Deprecated v1alpha2 Go types are now aliases to their v1beta1 versions
(#1390, @howardjohn)