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.6.2 to 0.7.1 #937

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 2, 2023

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

Release notes

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

v0.7.1

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

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:

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

... (truncated)

Changelog

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

v0.7.1

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

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:

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

... (truncated)

Commits
  • ab03a59 Merge pull request #2081 from robscott/changelog-v0.7.1
  • 27efbb5 Adding changelog for v0.7.1
  • 54bd466 Merge pull request #2068 from k8s-infra-cherrypick-robot/cherry-pick-2067-to-...
  • cd370d5 conformance: wait for namespace to be ready in TLSRoute test
  • e60faa0 Merge pull request #2059 from k8s-infra-cherrypick-robot/cherry-pick-2054-to-...
  • cc22914 Add method matching to HTTPRoute matching precedence order
  • 692afa8 Merge pull request #2056 from k8s-infra-cherrypick-robot/cherry-pick-2055-to-...
  • 9df33e5 Clarifying HTTPRoute exact match behavior
  • dfe12a7 Merge pull request #2053 from k8s-infra-cherrypick-robot/cherry-pick-2050-to-...
  • 5bc76ab docs: attachedRoutes comment updated
  • 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)

@dependabot dependabot bot added area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. labels Jun 2, 2023
@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jun 2, 2023
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 2, 2023
@k8s-ci-robot
Copy link
Contributor

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Jun 2, 2023
Bumps [sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 0.6.2 to 0.7.1.
- [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.6.2...v0.7.1)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/sigs.k8s.io/gateway-api-0.7.1 branch from 309a601 to f7fbd68 Compare June 7, 2023 13:06
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jun 7, 2023
@xing-yang
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 22, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], xing-yang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 22, 2023
@k8s-ci-robot k8s-ci-robot merged commit 19c11fa into master Jun 22, 2023
@dependabot dependabot bot deleted the dependabot/go_modules/sigs.k8s.io/gateway-api-0.7.1 branch June 22, 2023 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants