v1.3.0-rc.1 #3706
robscott
announced in
Announcements
v1.3.0-rc.1
#3706
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We expect that this release candidate is quite close to the final v1.3.0
release. However, subsequent breaking API changes are still possible.
This release candidate is suitable for implementors, but we do not recommend
shipping products based on a release candidate API due to the possibility of
incompatible changes prior to the final release. The following represents the
changes since v1.2.0:
Changes by Kind
Noteworthy Changes for Implementors
This section is intended to be a guide for API changes that might inspire or require implementation changes.
None of these API changes represent breaking changes.
OverlappingTLSConfig for Connection Coalescing
A new
OverlappingTLSConfigcondition has been added to Gateway Listeners to indicate situations whereConnection Coalescing could be problematic. The Gateway specification for handling Hostname and SNI matching for HTTPS
requests has been clarified and now recommends that implementations return 421 HTTP code responses in certain cases.
Move
BackendTLSPolicySubjectAltNamesfrom Core to ExtendedSubjectAltNamesfield ofBackendTLSPolicychanged from Core to Extended feature. (#3591,@mlavacca)The
backendReffilter must send traffic to the correct backends when weighted routing is configuredbackendReffilters don't affect weighted routing. (#3604,@dprotaso)Clarify reasons for certain object status conditions
parametersRefAcceptedcondition whenparametersRefis invalid. (#3579,@mlavacca)GatewayClassReasonInvalidParametersreason description. (#3553,@mlavacca)BackendTLSPolicy
BackendTLSPolicy. (#3496,@snorwin)GRPCRoute
GRPCRoutematch limit from 8 -> 64 (#3601,@EyalPazz)Gateway.Spec.Addresses changes
A new type
GatewaySpecAddressreplacesGatewayAddress. InGatewayAddresstheValuefield was required. InGatewaySpecAddresstheValuefield is optional. When theValueis unspecified, if an implementation supports that,it SHOULD automatically assign an address. If an implementation does not support an empty
Value, it MUST set theProgrammedcondition in status to false with a reason of "AddressNotAssigned". TheAddressesfield inGateway.Spechas changed from type[]GatewayAddressto[]GatewaySpecAddress.valuefield inGateway.Spec.Addressesarray optional (#3616,@EyalPazz)Standard Channel Additions and Changes
The Standard channel is Gateway API's set of maximally-stable install files.
Only features with the best testing and support are added to the standard
channel. This channel should be considered GA or stable, and future changes will
be fully backwards compatible.
Percentage-Based Request Mirroring 🎉
This feature enhances the existing request mirroring feature
by allowing users to specify a percentage of requests to be mirrored in both
HTTPRouteand
GRPCRouteobjects.This feature has graduated to Standard and is now considered GA or Stable.
This feature's name for conformance tests (and GatewayClass status reporting) is
HTTPRouteRequestPercentageMirror.This feature's status is Extended, meaning that it is optional for
implementations to support. If you're using Experimental Channel, you can refer
to the
supportedFeaturesfield in thestatusof any GatewayClass.Relevant PRs:
Experimental Channel Additions and Changes
The Experimental Channel is Gateway API's channel for testing out changes and
gaining confidence with them before allowing them to go to Standard.
This channel may include features that are changed or removed later!
CORS (Cross Origin Resource Sharing) Filter
GEP-1767 describes how to add
configuration of CORS filters on HTTPRoute objects, and in this release, this change
has moved to Experimental.
Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
HTTPRoute(#3637,@robscott)HTTPRouteFilter.CORS.AllowCredentialsto expect a boolean and not a string (#3656,@EyalPazz)HTTPRouteFilterType(#3668,@EyalPazz)XListenerSets (Standard Mechanism to Merge Gateways)
GEP-1713 defines a new mechanism to merge listeners into a single
Gateway, and in this release, this change has moved to Experimental. Following a new naming convention, an
experimental object name is prefaced with an X, thus
ListenerSethas changed toXListenerSet.The object group name has changed from
gateway.networking.k8s.iotogateway.networking.x-k8s.io.Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
ListenerSets across namespaces (#3632,@dprotaso)ListenerSetAPI & Generate Clients (in the group gateway.networking.k8s-x.io) (#3588,@dprotaso)ListenerSethas been renamed toXListenerSet. The ResourceBackendTrafficPolicyhas been renamed toXBackendTrafficPolicy. (#3682,@mlavacca)XBackendTrafficPolicy (Retry Budgets)
GEP-3388
specifies the configuration of a "retry budget" across all endpoints of a destination service in order to prevent
additional client-side retries after reaching a configured threshold. The budget can be configured using a maximum
percentage of active requests, or an interval during which requests will be considered. In this release, this change has
moved to Experimental. Following a new naming convention, an experimental object name is prefaced with an X, thus
BackendTrafficPolicyhas changed toXBackendTrafficPolicy. The object group name has changed fromgateway.networking.k8s.iotogateway.networking.x-k8s.io.Please see the GEP reference document or the API reference for the details.
This feature has graduated to Experimental and should now be used for testing
and verification purposes only. Experimental features may be changed or removed
in a future version.
This feature does not currently have a feature name defined.
This feature's status is Extended, meaning that it is optional for
implementations to support.
As there is no feature name or conformance testing available for this feature
yet, please check your implementation's documentation to see if it is supported.
Relevant PRs:
BackendTrafficPolicywith ability to configure budgeted retries (#3607,@ericdbishop)ListenerSethas been renamed toXListenerSet. The ResourceBackendTrafficPolicyhas been renamed toXBackendTrafficPolicy. (#3682,@mlavacca)budgetPercentandbudgetIntervaltobudget.percentand
budget.intervalrespectively. (#3695,@youngnick)GEPs
Documentation
InvalidParametersreason SHOULD be used with theAcceptedcondition in case the object referenced does not exist, is of an unsupported kind, or is malformed. (#3579,@mlavacca)sessionPersistence.cookieConfig.lifetimeType(#3540,@arkodg)(#3657,@blake),
(#3400,@jsoref),
(#3626,@zirain),
(#3565,@Vaniog),
(#3485,@fatsheep9146)
LocalObjectReference(empty string infers core API group) (#3597,@EyalPazz)Cleanup
Bug or Regression
HTTPCORSFilter.AllowMethods(#3667,@EyalPazz)
Dependencies
Added
Changed
k8s.io/kube-openapi: 8948a66 → 32ad38e
Removed
This discussion was created from the release v1.3.0-rc.1.
Beta Was this translation helpful? Give feedback.
All reactions