Bump sigs.k8s.io/gateway-api from 0.6.2 to 0.7.0

[dependabot]

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

Release notes

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

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:

• GEP-1323: Response Header Modifiers (#1905, @​robscott)
• GEP-726: Path Redirects and Rewrites (#1874, @​robscott)

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

GEP-713: Policy Attachment

This GEP received a major update, splitting policy attachment into two categories "Direct" and "Inherited". The new "Direct" mode enables a simplified form of policy attachment for targeting a single resource (#1565, @​youngnick).

GEP-1748: Gateway API Interaction with Multi-Cluster Services

A new GEP was introduced to define how Gateway API interacts with Multi-Cluster Services. At a high level, this states that ServiceImports have "Extended" support and can be used anywhere Services can throughout the API. There's a lot more nuance here, so for the full details, refer to the GEP. (#1843, @​robscott)

Other Changes by Kind

Status Changes

• The "Ready" Gateway and Listener condition has been reserved for future use. (#1888, @​howardjohn)
• The UnsupportedAddress Listener condition reason has been moved to a Gateway condition reason. (#1888, @​howardjohn)
• The AddressNotAssigned Gateway condition reasons has moved from Accepted to Programmed. (#1888, @​howardjohn)
• The NoResources Gateway condition reasons has moved from Ready to Programmed. (#1888, @​howardjohn)

Spec Cleanup

• Clarification that port redirects should not add port number to Location header for HTTP and HTTPS requests on 80 and 443. (#1908, @​robscott)
• Port redirect when empty will depend on the configured Redirect scheme (#1880, @​gauravkghildiyal)
• Updated spec to clarify that Exact matches have precedence over Prefix matches and RegularExpression matches have implementation specific precedence. (#1855,

... (truncated)

Changelog

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

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:

• GEP-1323: Response Header Modifiers (#1905, @​robscott)
• GEP-726: Path Redirects and Rewrites (#1905, @​robscott)

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

GEP-713: Policy Attachment

This GEP received a major update, splitting policy attachment into two categories "Direct" and "Inherited". The new "Direct" mode enables a simplified form of policy attachment for targeting a single resource (#1565, @​youngnick).

GEP-1748: Gateway API Interaction with Multi-Cluster Services

A new GEP was introduced to define how Gateway API interacts with Multi-Cluster Services. At a high level, this states that ServiceImports have "Extended" support and can be used anywhere Services can throughout the API. There's a lot more nuance here, so for the full details, refer to the GEP. (#1843, @​robscott)

Other Changes by Kind

Status Changes

• The "Ready" Gateway and Listener condition has been reserved for future use. (#1888, @​howardjohn)
• The UnsupportedAddress Listener condition reason has been moved to a Gateway condition reason. (#1888, @​howardjohn)
• The AddressNotAssigned Gateway condition reasons has moved from Accepted to Programmed. (#1888, @​howardjohn)
• The NoResources Gateway condition reasons has moved from Ready to Programmed. (#1888, @​howardjohn)

Spec Cleanup

• Clarification that port redirects should not add port number to Location header for HTTP and HTTPS requests on 80 and 443. (#1908, @​robscott)
• Port redirect when empty will depend on the configured Redirect scheme (#1880, @​gauravkghildiyal)
• Updated spec to clarify that Exact matches have precedence over Prefix matches

... (truncated)

Commits

• fea4334 Merge pull request #2023 from robscott/changelog-v0.7.0
• 2d1859d Adding changelog for v0.7.0 release
• 551baa6 Merge pull request #2022 from robscott/v0.7.0-fixes
• e568e2a Replacing fmt.Sprintln with plain strings
• ac5b0bb Merge pull request #2017 from keithmattix/mesh-conformance-fixes
• 2f86450 Merge pull request #2021 from kubernetes-sigs/dependabot/pip/mkdocs-awesome-p...
• f4b5650 Merge pull request #2020 from kubernetes-sigs/dependabot/pip/mkdocs-material-...
• f6e472a Merge pull request #2019 from kubernetes-sigs/dependabot/pip/tornado-6.3.2
• 3a1958a build(deps): bump mkdocs-awesome-pages-plugin from 2.9.0 to 2.9.1
• e8ee55e build(deps): bump mkdocs-material from 9.1.11 to 9.1.12
• 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 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)

[kate-osborn]

hold off reviewing - I need to update another doc

update: ready now