Bump sigs.k8s.io/gateway-api from 1.0.0 to 1.1.0

[dependabot]

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

Release notes

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

v1.1.0

On behalf of Kubernetes SIG Network, we are pleased to announce the v1.1 release! This release includes the graduation of several features to GA, including both GRPCRoute and Service Mesh. We are also introducing several new experimental features, including Session Persistence and Gateway Client Cert Verification.

The following represents the changes since v1.0.0:

Standard Channel

GRPCRoute has Graduated to GA 🎉

GRPCRoute has graduated to GA (v1) and is now part of the Standard Channel. If you are already using the experimental version GRPCRoute, we recommend holding off on upgrading to the standard channel version of GRPCRoute until the controllers you're using have been updated to support GRPCRoute v1. Until then, it is safe to upgrade to the experimental channel version of GRPCRoute in v1.1 that includes both v1alpha2 and v1 API versions.

Leading Contributor: @​gnossen

Service Mesh Support has Graduated to GA 🎉

The standard for using Gateway API for Mesh has formally graduated to GA (v1) and is now part of the Standard Channel.

Service mesh support in Gateway API allows service mesh users to use the same API to manage ingress traffic and mesh traffic, reusing the same policy and routing interfaces. In Gateway API v1.1, routes (such as HTTPRoute) can now have a Service as a parentRef, to control how traffic to specific services behave. For more information, read the service mesh documentation or see the list of implementations.

Leading Contributors: @​howardjohn, @​keithmattix, @​kflynn, @​mikemorris

Conformance Profiles and Reports

The Conformance Reports API and the corresponding test suite have been graduated to GA. The Conformance report API has been expanded with the mode field (intended to specify the working mode of the implementation), and the gatewayAPIChannel (standard or experimental). The gatewayAPIVersion and gatewayAPIChannel are now filled in automatically by the suite machinery, along with a brief description of the testing outcome. The Reports have been reorganized in a more structured way, and the implementations can now add information on how the tests have been run and provide reproduction steps.

Leading Contributors: @​mlavacca, @​shaneutt

ParentRef Port field Graduated to GA

... (truncated)

Changelog

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

Release Process

Overview

The Gateway API project is an API project that has the following two components:

• Kubernetes Custom Resource Definitions (CRDs)
• Corresponding Go API in the form of sigs.k8s.io/gateway-api Go package

This repository is the home for both of the above components.

Versioning strategy

The versioning strategy for this project is covered in detail in the release documentation.

Releasing a new version

Writing a Changelog

To simplify release notes generation, we recommend using the Kubernetes release notes generator:

go install k8s.io/release/cmd/release-notes@latest
export GITHUB_TOKEN=your_token_here
release-notes --start-sha EXAMPLE_COMMIT --end-sha EXAMPLE_COMMIT --branch main --repo gateway-api --org kubernetes-sigs

This output will likely need to be reorganized and cleaned up a bit, but it provides a good starting point. Once you're satisfied with the changelog, create a PR. This must go through the regular PR review process and get merged into the main branch. Approval of the PR indicates community consensus for a new release.

Release Steps

The following steps must be done by one of the [Gateway API maintainers][gateway-api-team]:

For a PATCH release:

• Create a new branch in your fork named something like <githubuser>/release-x.x.x. Use the new branch in the upcoming steps.
• Use git to cherry-pick all relevant PRs into your branch.
• Update pkg/generator/main.go with the new semver tag and any updates to the API review URL.
• Run the following command BASE_REF=vmajor.minor.patch make generate which will update generated docs with the correct version info. (Note that you can't test with these YAMLs yet as they contain references to elements which wont exist until the tag is cut and image is promoted to production registry.)
• Create a pull request of the <githubuser>/release-x.x.x branch into the release-x.x branch upstream (which should already exist since this is a patch release). Add a hold on this PR waiting for at least

... (truncated)

Commits

• 690f754 Adding changelog for v1.1.0 (#3062)
• a29ddd4 Contour conformance report updates (#3061)
• 70ef27e Splitting Changelogs for each minor version (#3060)
• 72e0a22 build(deps): bump sigs.k8s.io/controller-runtime in /gwctl (#3052)
• 95d865e SessionPersistence field should have omitempty tag (#3059)
• 6fc4f83 Adding changelog for v1.1.0-rc2 (#3046)
• c8218ff Conformance test for listener isolation (#3047)
• 654dde5 Make gwctl ReferenceGrant aware. Capture any errors observed while constructi...
• cd175ec Conformance display profiles on gatewayapi docs (#2874)
• ab850c3 Properly handle different versioned resources in gwctl (eg. v1beta1 v/s v1 AP...
• 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]

Looks like sigs.k8s.io/gateway-api is up-to-date now, so this is no longer needed.