build(deps): bump sigs.k8s.io/gateway-api from 0.8.1 to 1.0.0

[dependabot]

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

Release notes

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

v1.0.0

On behalf of Kubernetes SIG Network, we are pleased to announce the v1.0 release! This release marks a huge milestone for this project. Several key APIs are graduating to GA (generally available), while other significant features have been added to the Experimental channel.

It's been four years since this project began, and we would never have gotten here without the support of a dedicated and active community. The maintainers would like to thanks everyone who's contributed to Gateway API, whether in the form of commits to the repo, discussion, ideas, or general support. We literally couldn't have gotten this far without you.

This project is nowhere near finished, as you can see from the large amount of features being added into the Experimental Channel. With such a big set of things still to do, contributors and contributions are more vital than ever. Please feel welcome to join our community!!

Gateway, GatewayClass, and HTTPRoute are GA 🎉

Gateway, GatewayClass, and HTTPRoute have all graduated to GA with a v1 API version. Although these APIs will continue to grow with future additions, the versions of these resources available via the Standard Channel are stable and recommended for use in production. Many implementations are fully passing conformance tests that cover the functionality of each of these resources. These APIs are graduating to GA with only minor spec clarifications since the v0.8.0 release.

CEL Migration

Starting in v0.8.0, Gateway API CRDs now include CEL validation. In this release the validating webhook is no longer bundled with CRD installation. Instead we include a separate webhook-install.yaml file as part of the release artifacts.

If you're running Kubernetes 1.25+, we do not recommend installing the webhook and additionally suggest that you uninstall any previously installed versions of the webhook.

If you're still running Kubernetes 1.23 or 1.24, we recommend installing the webhook until you can upgrade to Kubernetes 1.25 or newer.

New Experimental Features

There are several exciting new experimental features in this release:

BackendTLSPolicy

A new BackendTLSPolicy resource has been introduced for configuring TLS connections from Gateways to Backends. This allows you to configure the Gateway to validate the certificates served by Backends. For more information, refer to GEP 1897.

... (truncated)

Changelog

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

v1.0.0

On behalf of Kubernetes SIG Network, we are pleased to announce the v1.0 release! This release marks a huge milestone for this project. Several key APIs are graduating to GA (generally available), while other significant features have been added to the Experimental channel.

It's been four years since this project began, and we would never have gotten here without the support of a dedicated and active community. The maintainers would like to thanks everyone who's contributed to Gateway API, whether in the form of commits to the repo, discussion, ideas, or general support. We literally couldn't have gotten this far without you.

This project is nowhere near finished, as you can see from the large amount of features being added into the Experimental Channel. With such a big set of things still to do, contributors and contributions are more vital than ever. Please feel welcome to join our community!!

Gateway, GatewayClass, and HTTPRoute are GA 🎉

Gateway, GatewayClass, and HTTPRoute have all graduated to GA with a v1 API version. Although these APIs will continue to grow with future additions, the versions of these resources available via the Standard Channel are stable and recommended for use in production. Many implementations are fully passing conformance tests that cover the functionality of each of these resources. These APIs are graduating to GA with only minor spec clarifications since the v0.8.0 release.

CEL Migration

Starting in v0.8.0, Gateway API CRDs now include CEL validation. In this release the validating webhook is no longer bundled with CRD installation. Instead we include a separate webhook-install.yaml file as part of the release artifacts.

If you're running Kubernetes 1.25+, we do not recommend installing the webhook and additionally suggest that you uninstall any previously installed versions of the webhook.

If you're still running Kubernetes 1.23 or 1.24, we recommend installing the webhook until you can upgrade to Kubernetes 1.25 or newer.

New Experimental Features

There are several exciting new experimental features in this release:

BackendTLSPolicy

A new BackendTLSPolicy resource has been introduced for configuring TLS connections from Gateways to Backends. This allows you to configure the Gateway to validate the certificates served by Backends. For more information, refer to

... (truncated)

Commits

• a068498 Merge pull request #2546 from youngnick/v1.0-changelog
• 5592c85 Fixing a couple typos + indentation
• f82ba55 Bumping versions to v1.0.0
• 6f15ea1 fix: nav for changelog
• b8b91df Apply suggestions from code review
• 6b43fe1 Create v1 changelog
• 8f1b718 Merge pull request #2545 from kubernetes-sigs/dependabot/pip/mkdocs-material-...
• f58ed7b build(deps): bump mkdocs-material from 9.4.6 to 9.4.7
• 5fd8bec Merge pull request #2535 from arkodg/rm-accepted
• 8cf18e3 Merge pull request #2534 from robscott/experimental-status
• 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)