v1.4.0 Release-Cycle: API Review, Release Candidates & Testing #4066
Replies: 5 comments 13 replies
-
|
Due to some timing issues that cropped up due to our need to provide extensions this release, as well as some timing issues around API review, we're not actually quite ready to cut an initial RC tag. We've created a release branch which includes all the current changes: https://github.com/kubernetes-sigs/gateway-api/tree/release-1.4 For the purposes of testing and reporting, please consider this "RC-like" as it is highly representative of what the first tag will be. We would appreciate testing and feedback on it from implementations. API review feedback changes and some final maintenance changes (notably, Please send any testing feedback, questions, etc about this as a reply to this comment, thank you! 🖖 |
Beta Was this translation helpful? Give feedback.
-
|
I've just LGTMed #3978, and I think that one should probably be backported into the release branch. I'll open a PR to do that if I can later today. |
Beta Was this translation helpful? Give feedback.
-
|
+1 I cherry-picked it in. |
Beta Was this translation helpful? Give feedback.
-
|
Our first pre-release and release candidate for Please check this out, run tests and conformance and supply any feedback in the comments here! 🖖 |
Beta Was this translation helpful? Give feedback.
-
|
@shaneutt is it on purpose that the CRD assets, e.g., |
Beta Was this translation helpful? Give feedback.
-
ACK. Thank you for reporting this.
I am not sure how this happened, but I re-uploaded the artifacts if that's working for you now please give a 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that the Airlock Microgateway successfully passes all conformance tests, including the new |
Beta Was this translation helpful? Give feedback.
-
|
While we haven't merged it yet, Istio is passing everything with |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thank you for the feedback. Looking to cut RC2 shortly, stay tuned. |
Beta Was this translation helpful? Give feedback.
-
|
Our second release candidate for Please check this out, run tests and conformance and supply any feedback in the comments here! 🖖 |
Beta Was this translation helpful? Give feedback.
-
|
I verified the fixes in |
Beta Was this translation helpful? Give feedback.
-
|
My in-flight v1.4 branch for Cilium also passed conformance for v1.4.0-rc.2, although I have not moved to the new conformance test framework yet, still passing SupportedFeatures for now (that move will come soon after this merges). |
Beta Was this translation helpful? Give feedback.
-
|
Have a WIP PR for adding 1.4 support to kgateway that's passing conformance. No major hurdles outside of the already mentioned issue john outlined in #4066 (reply in thread), the SSA hack when installing the new CRDs, and some issues relying where the project relies on types that were shifted around (mostly around BTP promotion) or documented as potential breaks (CORS, GatewayTLSConfig). |
Beta Was this translation helpful? Give feedback.
-
|
Updated NGINX Gateway Fabric to 1.4.0-rc2 in a branch and its passing conformance (including the new BackendTLSPolicy tests). There's a bit of work on our side for all the Policy types graduating to v1, but nothing we weren't expecting. |
Beta Was this translation helpful? Give feedback.
-
|
cloud-provider-kind with latest clients and CRDs is passing latest conformance kubernetes-sigs/cloud-provider-kind#295 |
Beta Was this translation helpful? Give feedback.
-
|
After RC1 and RC2 had good feedback (@kflynn did find a conformance CLI issue in RC2, but we've discussed and we will fix this as a follow-up) we're looking at the final release being Monday morning, October 5th 2025. |
Beta Was this translation helpful? Give feedback.
-
|
v1.4.0 is now released. Thank you to everyone in the community that came together to make this possible. 🎉 If you run into any issues with the release, please submit a bug report via GitHub issues, and/or let us know in Slack! 🖖 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
The API Refinement and Documentation Phase for Release v1.4.0 has concluded. We're now in the final stretch before the final release where we'll be doing continue review, testing, and publishing RCs.
As a reminder the following features have moved to
Standard:And these have moved to
Experimental:Implementers: During this phase, please run and generate reports for the conformance tests for the above features if your implementation intends to support them. We need feedback and reports for conformance tests from several implementations prior to the final release, as this helps with final confidence in the delivery. Please feel free to share feedback about conformance directly in this announcement as comments.
We will post updates here about release candidates, so please subscribe to this announcement for continued updates to stay tuned.
If you have questions, comments or concerns about this part of the release cycle or you need support with any of the features in this release: this thread is a great place to comment, ask for help and check in!
Beta Was this translation helpful? Give feedback.
All reactions