Bump sigs.k8s.io/gateway-api from 0.7.1 to 0.8.1

[dependabot]

Bumps sigs.k8s.io/gateway-api from 0.7.1 to 0.8.1.

Release notes

Sourced from sigs.k8s.io/gateway-api's releases.

v0.8.1

This is a patch release that includes small bug fixes and a new conformance test as a follow up to the v0.8.0 release.

Changes by Kind

Bug Fixes

• Fix CEL validation not handling missing listener hostname correctly. (#2370, @​frankbu)
• Fix IPv6 parsing in conformance tests (#2375, @​keithmattix)

Conformance Tests

• Add conformance test for multiple mirror filters. (#2359, @​levikobi)

v0.8.0

Major Themes

GAMMA (Service Mesh)

Service mesh support per the GAMMA initiative has moved to experimental in v0.8.0. As an experimental API, it is still possible that this will change; the working group does not recommend shipping products based on any experimental API.

When using the Gateway API to configure a service mesh, the Gateway and GatewayClass resources are not used (as there will typically only be one mesh in the cluster) and, instead, individual route resources are associated directly with Service resources. This permits configuring mesh routing while preserving the Gateway API's overall semantics.

We encourage service mesh implementers and users to try this new support and we welcome feedback! Once again, though, the working group does not recommend shipping products based on this or any other experimental API. due to the possibility of incompatible changes prior to the final release.

CEL Validation

This release marks the beginning of a transition from webhook validation to CEL validation that is built into the CRDs. That will mean different things depending on the version of Kubernetes you're using:

Kubernetes 1.25+

CEL validation is fully supported. Most validation is now covered by the validating webhook, but unfortunately not quite everything.

All but one validation has been translated from the webhook to CEL. Currently the CRDs only have a case-sensitive uniqueness check for header names in header modifier filters. The webhook validation is more thorough, ensuring that the uniqueness is case-insensitive. Unfortunately that

... (truncated)

Changelog

Sourced from sigs.k8s.io/gateway-api's changelog.

v0.8.1

This is a patch release that includes small bug fixes and a new conformance test as a follow up to the v0.8.0 release.

Changes by Kind

Bug Fixes

• Fix CEL validation not handling missing listener hostname correctly. (#2370, @​frankbu)
• Fix IPv6 parsing in conformance tests (#2375, @​keithmattix)

Conformance Tests

• Add conformance test for multiple mirror filters. (#2359, @​levikobi)

v0.8.0

Major Themes

GAMMA (Service Mesh)

Service mesh support per the GAMMA initiative has moved to experimental in v0.8.0. As an experimental API, it is still possible that this will change; the working group does not recommend shipping products based on any experimental API.

When using the Gateway API to configure a service mesh, the Gateway and GatewayClass resources are not used (as there will typically only be one mesh in the cluster) and, instead, individual route resources are associated directly with Service resources. This permits configuring mesh routing while preserving the Gateway API's overall semantics.

We encourage service mesh implementers and users to try this new support and we welcome feedback! Once again, though, the working group does not recommend shipping products based on this or any other experimental API. due to the possibility of incompatible changes prior to the final release.

CEL Validation

This release marks the beginning of a transition from webhook validation to CEL validation that is built into the CRDs. That will mean different things depending on the version of Kubernetes you're using:

Kubernetes 1.25+

CEL validation is fully supported. Most validation is now covered by the validating webhook, but unfortunately not quite everything.

All but one validation has been translated from the webhook to CEL. Currently the CRDs only have a case-sensitive uniqueness check for header names in header modifier filters. The webhook validation is more

... (truncated)

Commits

• 78ed734 Merge pull request #2395 from frankbu/multi-mirrors
• 3ba04ed Fix multiple mirror conformance test
• 759e09e Merge pull request #2392 from youngnick/update-gep-1742
• c99f726 Merge pull request #2384 from robscott/version-skew
• e2ecde4 Move GEP-1742 to experimental
• 3fa4a94 Merge pull request #2389 from pmalek/update-conformance-reports-latest-link
• c63aa6c Merge pull request #2282 from Xunzhuo/add-eg-report
• b858494 Merge pull request #2390 from mlavacca/fix-makefile-experimental
• 3f3b000 chore: remove conformance/reports/latest link
• 4a8f5de chore: removed experimental tag from Makefile
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #1049.