Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump sigs.k8s.io/gateway-api from 0.5.1 to 0.6.0 #10038

Merged
merged 7 commits into from
Jan 16, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 22, 2022

Bumps sigs.k8s.io/gateway-api from 0.5.1 to 0.6.0.

Release notes

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

v0.6.0

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.

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:

... (truncated)

Changelog

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

v0.6.0

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.

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:

... (truncated)

Commits
  • 6c222d3 chore: update default version to v0.6.0
  • ca470e2 Merge pull request #1614 from shaneutt/shaneutt/v0.6.0-changelog
  • 9522bd0 docs: add v0.6.0 changelog entry
  • 6a8738a Merge pull request #1594 from youngnick/973-fix
  • 05fa505 Update wording on ParentRef field to require AllowedRoutes or ReferenceGrant
  • dc314b1 Assert observedGeneration is incremented in Status.Conditions. (#1586)
  • 9c9429a Merge pull request #1609 from frankbu/impl/istio
  • 889b226 Merge pull request #1608 from shaneutt/shaneutt/release-v060-rc2
  • 91d868b chore: update webhook version in build hacks
  • 3c693e0 fix link target
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 0.5.1 to 0.6.0.
- [Release notes](https://github.com/kubernetes-sigs/gateway-api/releases)
- [Changelog](https://github.com/kubernetes-sigs/gateway-api/blob/main/CHANGELOG.md)
- [Commits](kubernetes-sigs/gateway-api@v0.5.1...v0.6.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/gateway-api
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner December 22, 2022 03:02
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Dec 22, 2022
In v0.26.0 client-go's `AddEventHandler` method for informers started
returning a registration handle (that we ignore) and an error that we
now surface up.
@alpeb
Copy link
Member

alpeb commented Dec 23, 2022

This pulls an update to client-go to v0.26.0, where the informers AddEventHandler method started returning a registration handle and an error. The linter was complaining we weren't accounting for those returned values, so in my last commit I capture them, surfacing the error, but still ignoring the returned handler.

Copy link
Member

@adleong adleong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this bump to client-go version affect our minimum or maximum supported k8s versions at all?

- Adds an innocuous change to integration.yml so that all tests get
  triggered
- Hard-code k8s version in `k3d cluster create` invocation to v1.21
@alpeb alpeb force-pushed the dependabot/go_modules/sigs.k8s.io/gateway-api-0.6.0 branch from 36ccbcd to 3e1fdd0 Compare January 11, 2023 15:14
@alpeb
Copy link
Member

alpeb commented Jan 11, 2023

Does this bump to client-go version affect our minimum or maximum supported k8s versions at all?

Good question. The client-go docs aren't clear about this. I temporarily forced all tests to run under k8s v1.21 in 3e1fdd0 (note test-policy and test-multicluster are already testing min and max k8s versions), and they appeared fine.

@alpeb alpeb merged commit 62d6d7c into main Jan 16, 2023
@alpeb alpeb deleted the dependabot/go_modules/sigs.k8s.io/gateway-api-0.6.0 branch January 16, 2023 14:38
alpeb added a commit that referenced this pull request Sep 6, 2023
…0038)

* build(deps): bump sigs.k8s.io/gateway-api from 0.5.1 to 0.6.0

** NOTE **
This was cherry-picked from 62d6d7c in
order to acquire the `AddEventHandler` changes that went there. The
actualy gateway-api bump was discarded.

Bumps [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 0.5.1 to 0.6.0.
- [Release notes](https://github.com/kubernetes-sigs/gateway-api/releases)
- [Changelog](https://github.com/kubernetes-sigs/gateway-api/blob/main/CHANGELOG.md)
- [Commits](kubernetes-sigs/gateway-api@v0.5.1...v0.6.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/gateway-api
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* Account for possible errors returned from `AddEventHandler`

In v0.26.0 client-go's `AddEventHandler` method for informers started
returning a registration handle (that we ignore) and an error that we
now surface up.

* client-go v0.26.0 removed the openstack plugin

* Temporary changes to trigger tests in k8s 1.21

- Adds an innocuous change to integration.yml so that all tests get
  triggered
- Hard-code k8s version in `k3d cluster create` invocation to v1.21

* Revert "Temporary changes to trigger tests in k8s 1.21"

This reverts commit 3e1fdd0.

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Alejandro Pedraza <[email protected]>
mateiidavid pushed a commit that referenced this pull request Sep 8, 2023
* build(deps): NOT bump sigs.k8s.io/gateway-api from 0.5.1 to 0.6.0 (#10038)

* build(deps): bump sigs.k8s.io/gateway-api from 0.5.1 to 0.6.0

** NOTE **
This was cherry-picked from 62d6d7c in
order to acquire the `AddEventHandler` changes that went there. The
actualy gateway-api bump was discarded.

Bumps [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 0.5.1 to 0.6.0.
- [Release notes](https://github.com/kubernetes-sigs/gateway-api/releases)
- [Changelog](https://github.com/kubernetes-sigs/gateway-api/blob/main/CHANGELOG.md)
- [Commits](kubernetes-sigs/gateway-api@v0.5.1...v0.6.0)

---
updated-dependencies:
- dependency-name: sigs.k8s.io/gateway-api
  dependency-type: direct:production
  update-type: version-update:semver-minor
...


* Account for possible errors returned from `AddEventHandler`

* client-go v0.26.0 removed the openstack plugin

* Fix memory leak in service mirror (#10833)


* Bump go to 1.19 in go.mod

---------

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: tomasz.ziolkowski <[email protected]>
Signed-off-by: Alejandro Pedraza <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Oliver Gould <[email protected]>
Co-authored-by: ziollek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants