dependabot[bot] opened a new pull request, #1945:
URL: https://github.com/apache/apisix-ingress-controller/pull/1945

   Bumps 
[sigs.k8s.io/gateway-api](https://github.com/kubernetes-sigs/gateway-api) from 
0.6.2 to 0.8.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/kubernetes-sigs/gateway-api/releases";>sigs.k8s.io/gateway-api's
 releases</a>.</em></p>
   <blockquote>
   <h2>v0.8.0</h2>
   <h2>Major Themes</h2>
   <h3>GAMMA (Service Mesh)</h3>
   <p>Service mesh support per the GAMMA initiative has moved to 
<strong>experimental</strong> in
   <code>v0.8.0</code>. As an experimental API, <strong>it is still possible 
that this will
   change</strong>; the working group does not recommend shipping products 
based on any
   experimental API.</p>
   <p>When using the Gateway API to configure a service mesh, the Gateway and
   GatewayClass resources are not used (as there will typically only be one mesh
   in the cluster) and, instead, individual route resources are associated
   directly with Service resources. This permits configuring mesh routing while
   preserving the Gateway API's overall semantics.</p>
   <p>We encourage service mesh implementers and users to try this new support 
and
   we welcome feedback! Once again, though, the working group does not recommend
   shipping products based on this or any other experimental API. due to the
   possibility of incompatible changes prior to the final release.</p>
   <h3>CEL Validation</h3>
   <p>This release marks the beginning of a transition from webhook validation 
to CEL
   validation that is built into the CRDs. That will mean different things
   depending on the version of Kubernetes you're using:</p>
   <h4>Kubernetes 1.25+</h4>
   <p>CEL validation is fully supported. Most validation is now covered by the
   validating webhook, but unfortunately not quite everything.</p>
   <p>All but one validation has been translated from the
   webhook to CEL. Currently the CRDs only have a case-sensitive uniqueness 
check
   for header names in header modifier filters. The webhook validation is more
   thorough, ensuring that the uniqueness is case-insensitive. Unfortunately 
that
   is not possible to represent with CEL today. There is more information in
   <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2277";>#2277</a>.</p>
   <p>Installing the validating webhook is still recommended for this release 
to allow
   controllers to catch up to cover this gap in CEL validation. We expect this 
is
   the last release we will make this recommendation for, for more information,
   refer to <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2319";>#2319</a>.</p>
   <h4>Kubernetes 1.23 and 1.24</h4>
   <p>CEL validation is not supported, but Gateway API v0.8.0 CRDs can still be
   installed. When you upgrade to Kubernetes 1.25+, the validation included in
   these CRDs will automatically take effect. We recommend continuing to install
   the validating webhook on these Kubernetes versions.</p>
   <h4>Kubernetes 1.22 and older</h4>
   <p>Unfortunately Gateway API v0.8.0 is not supported on these Kubernetes 
versions.</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/kubernetes-sigs/gateway-api/blob/main/CHANGELOG.md";>sigs.k8s.io/gateway-api's
 changelog</a>.</em></p>
   <blockquote>
   <h1>v0.8.0</h1>
   <h2>Major Themes</h2>
   <h3>GAMMA (Service Mesh)</h3>
   <p>Service mesh support per the GAMMA initiative has moved to 
<strong>experimental</strong> in
   <code>v0.8.0</code>. As an experimental API, <strong>it is still possible 
that this will
   change</strong>; the working group does not recommend shipping products 
based on any
   experimental API.</p>
   <p>When using the Gateway API to configure a service mesh, the Gateway and
   GatewayClass resources are not used (as there will typically only be one mesh
   in the cluster) and, instead, individual route resources are associated
   directly with Service resources. This permits configuring mesh routing while
   preserving the Gateway API's overall semantics.</p>
   <p>We encourage service mesh implementers and users to try this new support 
and
   we welcome feedback! Once again, though, the working group does not recommend
   shipping products based on this or any other experimental API. due to the
   possibility of incompatible changes prior to the final release.</p>
   <h3>CEL Validation</h3>
   <p>This release marks the beginning of a transition from webhook validation 
to CEL
   validation that is built into the CRDs. That will mean different things
   depending on the version of Kubernetes you're using:</p>
   <h4>Kubernetes 1.25+</h4>
   <p>CEL validation is fully supported. Most validation is now covered by the
   validating webhook, but unfortunately not quite everything.</p>
   <p>All but one validation has been translated from the
   webhook to CEL. Currently the CRDs only have a case-sensitive uniqueness 
check
   for header names in header modifier filters. The webhook validation is more
   thorough, ensuring that the uniqueness is case-insensitive. Unfortunately 
that
   is not possible to represent with CEL today. There is more information in
   <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2277";>#2277</a>.</p>
   <p>Installing the validating webhook is still recommended for this release 
to allow
   controllers to catch up to cover this gap in CEL validation. We expect this 
is
   the last release we will make this recommendation for, for more information,
   refer to <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2319";>#2319</a>.</p>
   <h4>Kubernetes 1.23 and 1.24</h4>
   <p>CEL validation is not supported, but Gateway API v0.8.0 CRDs can still be
   installed. When you upgrade to Kubernetes 1.25+, the validation included in
   these CRDs will automatically take effect. We recommend continuing to install
   the validating webhook on these Kubernetes versions.</p>
   <h4>Kubernetes 1.22 and older</h4>
   <p>Unfortunately Gateway API v0.8.0 is not supported on these Kubernetes 
versions.</p>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/3d22aa5a08413222cb79e6b2e245870360434614";><code>3d22aa5</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2360";>#2360</a>
 from robscott/changelog-v0.8.0</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/645b165b92b21a9bc7c88335f4e23d73c7554178";><code>645b165</code></a>
 Adding v0.8.0 changelog</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/5d4a870d2b27d21389fbafc6b6953854a23a2283";><code>5d4a870</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2315";>#2315</a>
 from gcs278/fix-gep-link</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/ad75c724bd5366cb23db35f982c5af3c9b8efc19";><code>ad75c72</code></a>
 Fix broken links to GEPs</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/2ed94864e539c0c39469f88116509c71afb26f7e";><code>2ed9486</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2358";>#2358</a>
 from gauravkghildiyal/tcp-leaks</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/4f8e57284ea8a26aebb09f701acd902493880662";><code>4f8e572</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2327";>#2327</a>
 from sayboras/tam/remove-experiment-tag</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/ddd0fd2795b996a5effd2cb5048a9f77b62415fb";><code>ddd0fd2</code></a>
 fix leaking TCP connections in conformance tests</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/74562ef7870f2b107c89a4ad0600c88696457578";><code>74562ef</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2351";>#2351</a>
 from kubernetes-sigs/dependabot/pip/mkdocs-material-...</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/c376a9ad11b2294f78dd1731c7e52c45a963e0dc";><code>c376a9a</code></a>
 Merge pull request <a 
href="https://redirect.github.com/kubernetes-sigs/gateway-api/issues/2352";>#2352</a>
 from kubernetes-sigs/dependabot/go_modules/sigs.k8s....</li>
   <li><a 
href="https://github.com/kubernetes-sigs/gateway-api/commit/a5bc0dc246acdcc57f03c365d46953a92a8a6b54";><code>a5bc0dc</code></a>
 build(deps): bump sigs.k8s.io/controller-runtime from 0.15.1 to 0.16.0</li>
   <li>Additional commits viewable in <a 
href="https://github.com/kubernetes-sigs/gateway-api/compare/v0.6.2...v0.8.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sigs.k8s.io/gateway-api&package-manager=go_modules&previous-version=0.6.2&new-version=0.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   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-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   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)
   
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to