Fix: support Gateway API v1.3.0#7835
Conversation
c2cc53a to
8fb5f2b
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #7835 +/- ##
==========================================
- Coverage 72.77% 72.66% -0.12%
==========================================
Files 235 235
Lines 35092 35181 +89
==========================================
+ Hits 25538 25563 +25
- Misses 7738 7802 +64
Partials 1816 1816 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
380e083 to
a22307b
Compare
Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
Signed-off-by: Huabing Zhao <zhaohuabing@gmail.com>
59aa15d to
7db02f0
Compare
7db02f0 to
3023af8
Compare
|
Close this in favor of #7523 |
|
Reopen this as a draft, we might want to test Gateway v1.3.0 CRDs with EG v1.6 if we'd like to officially support multiple Gateway API versions. |
|
This pull request has been automatically marked as stale because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, when it's ready. Thank you for your contributions! |
|
Closing this as it can break the upgrade path from experimental to standard channel. |
This PR adds support for the Gateway API v1.3.0 experimental channel CRDs in the main branch.
The only CRD that requires backward compatibility handling is BackendTLSPolicy, which has graduated from v1alpha3 to the standard channel (v1).
It also adds e2e tests for Gateway API v1.3.0.
We do not add tests for v1.4.0, since there are no API changes between Gateway API v1.4.0 and v1.4.1—the latter only includes a bug fix related to the BackendTLSPolicy status.
Fixes: #7709