Service Apis Versions Save

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

v0.7.1

1 year ago

This is a patch release that includes small fixes, clarifications, and conformance tests as a follow up to the v0.7.0 release.

Changes by Kind

Conformance Tests

  • Fixed an issues causing conformance tests to fail when using IPv6 addresses. (#2024, @howardjohn)
  • HTTPRoute connectivity is in now enforced in conformance tests if a relevant ReferenceGrant gets deleted. (#1853, @pmalek)
  • New: Conformance tests for HTTP request mirroring. (#1912, @liorlieberman)
  • Fixes to port and scheme redirect tests: Tests now send HTTPS requests with consistent SNI and Host, Gateway now has the correct SANs. (#2039, @sunjaybhatia)
  • TLSRoute test now waits for namespaces to be ready. (#2067, @skriss)

Validating Webhook

  • Webhook config works with "restricted" Pod Security level. (#2016, @jcpunk)

Clarifications

  • HTTPRoute Method matching precedence has been clarified. (#2054, @gauravkghildiyal)
  • Implementations MUST ignore any port value specified in the HTTP Host header while performing a match against HTTPRoute.Hostnames. (#1980, @gauravkghildiyal)
  • HTTPRoute: Clarified that exact path matches are truly exact, both trailing slashes and capitalization are meaningful. (#2055, @robscott)
  • Gateway: Clarified that AttachedRoutes should only consider Routes that have been accepted. (#2050, @mlavacca)

v0.7.0

1 year ago

The v0.7.0 release focuses on refining and stabilizing existing APIs. This included a focus on both conformance tests and clarifying ambiguous parts of the API spec.

Features Graduating to Standard

In addition to those broad focuses, 2 features are graduating to the standard channel:

  • GEP-1323: Response Header Modifiers (#1905, @robscott)
  • GEP-726: Path Redirects and Rewrites (#1874, @robscott)

GEPs

There are a lot of interesting GEPs in the pipeline right now, but only some of these GEPs have made it to experimental status in time for v0.7.0. The GEPs highlighted below are both in an experimental state and are either entirely new (GEP-1748) or had significant new concepts introduced (GEP-713):

GEP-713: Policy Attachment

This GEP received a major update, splitting policy attachment into two categories "Direct" and "Inherited". The new "Direct" mode enables a simplified form of policy attachment for targeting a single resource (#1565, @youngnick).

GEP-1748: Gateway API Interaction with Multi-Cluster Services

A new GEP was introduced to define how Gateway API interacts with Multi-Cluster Services. At a high level, this states that ServiceImports have "Extended" support and can be used anywhere Services can throughout the API. There's a lot more nuance here, so for the full details, refer to the GEP. (#1843, @robscott)

Other Changes by Kind

Status Changes

  • The "Ready" Gateway and Listener condition has been reserved for future use. (#1888, @howardjohn)
  • The UnsupportedAddress Listener condition reason has been moved to a Gateway condition reason. (#1888, @howardjohn)
  • The AddressNotAssigned Gateway condition reasons has moved from Accepted to Programmed. (#1888, @howardjohn)
  • The NoResources Gateway condition reasons has moved from Ready to Programmed. (#1888, @howardjohn)

Spec Cleanup

  • Clarification that port redirects should not add port number to Location header for HTTP and HTTPS requests on 80 and 443. (#1908, @robscott)
  • Port redirect when empty will depend on the configured Redirect scheme (#1880, @gauravkghildiyal)
  • Updated spec to clarify that Exact matches have precedence over Prefix matches and RegularExpression matches have implementation specific precedence. (#1855, @Xunzhuo)
  • The gateway-exists-finalizer.gateway.networking.k8s.io finalizer is no longer required and is now just recommended. (#1917, @howardjohn)

Validation Fixes

  • Removes GRPCRoute method match defaulting to allow for matching all requests, or matching only by header. (#1753, @skriss)
  • Update route validation to comply with RFC-3986 "p-char" characters. (#1644, @jackstine)
  • Illegal names like " " will be not allowed for query param name in HTTPQueryParamMatch. (#1796, @gyohuangxin)
  • Webhook: Port is now considered when validating that ParentRefs are unique (#1995, @howardjohn)

Conformance

  • No conformance tests run by default anymore, including tests for GatewayClass and Gateway. A new SupportGateway feature must be opted into in order to run those tests (similar to what we've done previously for ReferenceGrant and HTTPRoute). Also with this release, EnableAllSupportedFeatures enables all Gateway AND Mesh features (where previously that was just Gateway). (#1894, @shaneutt)
  • Gateways must publish the "Programmed" condition. (#1732, @robscott)
  • Add all-features flag to enable all supported feature conformance tests. (#1642, @gyohuangxin)
  • A new SkipTests field has been added to the conformance test options to opt-out of specific tests. (#1578, @mlavacca)
  • Added: conformance tests for http rewrite host and path filters. (#1622, @LiorLieberman)
  • In Conformance tests, when a Route references a gateway having no listener whose allowedRoutes criteria permit the route, the reason NotAllowedByListeners should be used for the accepted condition. (#1669, @mlavacca)
  • Support configurable timeout for GatewayObservedGenerationBump (#1887, @Xunzhuo)
  • The conformance test HTTPRouteInvalidCrossNamespaceParentRef now requires the HTTPRoute accepted condition to be failing with the ParentRefNotPermitted reason. (#1694, @mlavacca)
  • The conformance tests always check that the HTTPRoute ResolvedRefs condition is enforced, even when the status is true. (#1668, @mlavacca)
  • Checks for the NotAllowedByListeners reason on the HTTPRoute's Accepted: false condition in the HTTPRouteInvalidCrossNamespaceParentRef conformance test. (#1714, @skriss)
  • Added conformance test to verify that path matching precedence is implemented correctly. (#1855, @Xunzhuo)
  • Remove a test that only covered redirect status without any other changes. (#2007, @robscott)
  • Port redirect when empty will depend on the configured Redirect scheme (#1880, @gauravkghildiyal)
  • Fixes for mesh conformance tests (#2017, @keithmattix)

Documentation

  • Updated outdated content on list of resources in installation guide page. (#1857, @randmonkey)
  • Fix description of ReferenceGrant example in documentation by making it use the correct resources. (#1864, @matteoolivi)
  • Fix grammar mistake in ReferenceGrant implementation guidelines. (#1865, @matteoolivi)

v0.7.0-rc2

1 year ago

We expect this to be our final release candidate before launching v0.7.0. This release candidate includes a variety of clarifications and conformance updates. The changelog below represents the changes since v0.7.0-rc1.

Changes by Kind

Spec Clarification

  • Port redirect when empty will depend on the configured Redirect scheme (#1880, @gauravkghildiyal)

Conformance

  • Remove a test that only covered redirect status without any other changes. (#2007, @robscott)
  • Port redirect when empty will depend on the configured Redirect scheme (#1880, @gauravkghildiyal)

Validation Fixes

  • Webhook: Port is now considered when validating that ParentRefs are unique (#1995, @howardjohn)

v0.7.0-rc1

1 year ago

Changes by Kind

Graduating to Standard

  • GEP-1323: Response Header Modifier has graduated to standard (#1905, @robscott)
  • GEP-726: Path Redirects and Rewrites has graduated to the standard channel. (#1874, @robscott)

Experimental GEPs

  • The Policy Attachment GEP received a major update, splitting policy attachment into two categories "Direct" and "Inherited". The new "Direct" mode enables a simplified form of policy attachment for targeting a single resource (#1565, @youngnick)
  • A new GEP was introduced to define how Gateway API interacts with Multi-Cluster Services (#1843, @robscott)

Status Changes

  • The "Ready" Gateway and Listener condition has been reserved for future use. (#1888, @howardjohn)
  • The UnsupportedAddress Listener condition reason has been moved to a Gateway condition reason. (#1888, @howardjohn)
  • The AddressNotAssigned Gateway condition reasons has moved from Accepted to Programmed. (#1888, @howardjohn)
  • The NoResources Gateway condition reasons has moved from Ready to Programmed. (#1888, @howardjohn)

Spec Cleanup

  • Clarification that port redirects should not add port number to Location header for HTTP and HTTPS requests on 80 and 443. (#1908, @robscott)
  • Updated spec to clarify that Exact matches have precedence over Prefix matches and RegularExpression matches have implementation specific precedence. (#1855, @Xunzhuo)
  • The gateway-exists-finalizer.gateway.networking.k8s.io finalizer is no longer required and is now just recommended. (#1917, @howardjohn)

Validation Fixes

  • Removes GRPCRoute method match defaulting to allow for matching all requests, or matching only by header. (#1753, @skriss)
  • Update route validation to comply with RFC-3986 "p-char" characters. (#1644, @jackstine)
  • Illegal names like " " will be not allowed for query param name in HTTPQueryParamMatch. (#1796, @gyohuangxin)

Conformance

  • No conformance tests run by default anymore, including tests for GatewayClass and Gateway. A new SupportGateway feature must be opted into in order to run those tests (similar to what we've done previously for ReferenceGrant and HTTPRoute). Also with this release, EnableAllSupportedFeatures enables all Gateway AND Mesh features (where previously that was just Gateway). (#1894, @shaneutt)
  • Gateways must publish the "Programmed" condition. (#1732, @robscott)
  • Add all-features flag to enable all supported feature conformance tests. (#1642, @gyohuangxin)
  • A new SkipTests field has been added to the conformance test options to opt-out of specific tests. (#1578, @mlavacca)
  • Added: conformance tests for http rewrite host and path filters. (#1622, @LiorLieberman)
  • In Conformance tests, when a Route references a gateway having no listener whose allowedRoutes criteria permit the route, the reason NotAllowedByListeners should be used for the accepted condition. (#1669, @mlavacca)
  • Support configurable timeout for GatewayObservedGenerationBump (#1887, @Xunzhuo)
  • The conformance test HTTPRouteInvalidCrossNamespaceParentRef now requires the HTTPRoute accepted condition to be failing with the ParentRefNotPermitted reason. (#1694, @mlavacca)
  • The conformance tests always check that the HTTPRoute ResolvedRefs condition is enforced, even when the status is true. (#1668, @mlavacca)
  • Checks for the NotAllowedByListeners reason on the HTTPRoute's Accepted: false condition in the HTTPRouteInvalidCrossNamespaceParentRef conformance test. (#1714, @skriss)
  • Added conformance test to verify that path matching precedence is implemented correctly. (#1855, @Xunzhuo)

Documentation

  • Updated outdated content on list of resources in installation guide page. (#1857, @randmonkey)
  • Fix description of ReferenceGrant example in documentation by making it use the correct resources. (#1864, @matteoolivi)
  • Fix grammar mistake in ReferenceGrant implementation guidelines. (#1865, @matteoolivi)

v0.6.2

1 year ago

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

Bug Fixes

  • Fix invalid HTTP redirect/rewrite examples. (#1787, @Xunzhuo)

Conformance Test Updates

  • The HTTPRouteInvalidCrossNamespaceParentRef conformance test now checks for the NotAllowedByListeners reason on the HTTPRoute's Accepted: false condition to better indicate why the route was note accepted. (#1714, @skriss)
  • A conformance test was added for HTTPRoute to cover the behavior of a non-matching SectionName similar to what was already present for ListenerPort. (#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 ObservedGeneration has 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 AttachedRoutes testing 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)

v0.6.1

1 year ago

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: https://github.com/kubernetes-sigs/gateway-api/compare/v0.6.0...v0.6.1

v0.6.0

1 year ago

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)

New Contributors

Full Changelog: https://github.com/kubernetes-sigs/gateway-api/compare/v0.5.0...v0.6.0

v0.6.0-rc2

1 year ago

What's Changed

We expect this to be our final release candidate before launching v0.6.0. This release candidate includes a variety of cleanup and documentation updates. The changelog below represents the changes since v0.6.0-rc1.

Conformance Tests

  • A new test has been added to cover HTTP Redirects (#1556, @LiorLieberman)
  • Fix Gateway reference in HTTPRouteInvalidParentRefNotMatchingListenerPort (#1591, @sayboras)

General Cleanup

  • Display the Programmed condition instead of the Ready condition in the output of kubectl get gateways. (#1602, @skriss)
  • GRPCRoute: Regex validation for Method and Service has been tightened to match GRPC spec. (#1599, @robscott)
  • GRPCRoute: Webhook validation of GRPCRoute has been expanded to closely match HTTPRoute validation. (#1599, @robscott)
  • HTTPRoute and Gateway: Gaps between webhook validation for v1alpha2 and v1beta1 have been closed. (#1599, @robscott)
  • 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)
  • The Gateway default conditions list now includes the Programmed condition. (#1604, @youngnick)
  • RegularExpression type selectors have been clarified to all be ImplementationSpecific conformance. (#1604, @youngnick)

New Contributors

Full Changelog: https://github.com/kubernetes-sigs/gateway-api/compare/v0.6.0-rc1...v0.6.0-rc2

v0.6.0-rc1

1 year ago

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)

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)

Developer Notes

  • Deprecated v1alpha2 Go types are now aliases to their v1beta1 versions (#1390, @howardjohn)
  • Moved type translation helpers from the utils package to a new package named translator. (#1337, @carlisia)

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)

v0.5.1

API versions: v1beta1, v1alpha2

This release includes a number of bug fixes and clarifications:

API Spec

  • The spec has been clarified to state that the port specified in BackendRef refers to the Service port number, not the target port, when a Service is referenced. #1332
  • The spec has been clarified to state that "Accepted" should be used instead of "Attached" on HTTPRoute. #1382

Webhook:

  • The duplicate gateway-system namespace definitions have been removed. #1387
  • The webhook has been updated to watch v1beta1. #1365

Conformance:

  • The expected condition for a cross-namespace certificate reference that has not been allowed by a ReferenceGrant has been changed from "InvalidCertificateRef" to "RefNotPermitted" to more closely match the spec. #1351
  • A new test has been added to cover when a Gateway references a Secret that does not exist #1334

v0.5.1

1 year ago

API versions: v1beta1, v1alpha2

This release includes a number of bug fixes and clarifications:

API Spec

  • The spec has been clarified to state that the port specified in BackendRef refers to the Service port number, not the target port, when a Service is referenced. #1332
  • The spec has been clarified to state that "Accepted" should be used instead of "Attached" on HTTPRoute. #1382

Webhook:

  • The duplicate gateway-system namespace definitions have been removed. #1387
  • The webhook has been updated to watch v1beta1. #1365

Conformance:

  • The expected condition for a cross-namespace certificate reference that has not been allowed by a ReferenceGrant has been changed from "InvalidCertificateRef" to "RefNotPermitted" to more closely match the spec. #1351
  • A new test has been added to cover when a Gateway references a Secret that does not exist #1334