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
Transition from SPDY to WebSockets #4006
Comments
/sig api-machinery |
/sig cli |
/milestone v1.28 |
Hello @seans3 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
Hello. Since the PRR reviewer @deads2k approved the KEP and since the KEP has been merged, I believe this KEP is now ready for v1.28. Please let me know if there are any other tasks needed for this release. Thanks. |
Hello @seans3! 1.28 Docs Shadow here. Does this enhancement work planned for 1.28 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hey @seans3 , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
Hey again @seans3 👋 I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above. As always, we are here to help if any questions come up. Thanks! |
Hello @seans3 👋, 1.28 Enhancements Lead here. Unfortunately, the implementation (code related) PRs associated with this enhancement are not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.28 milestone. If you still wish to progress this enhancement in v1.28, please file an exception request. Thanks! /milestone clear |
Hello @seans3 👋, 1.29 Enhancements team here! Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, please update the The status of this enhancement is marked as Thank you! |
that doesn't really make sense... the KEP is still in alpha and is remaining implementable for 1.29 in alpha, not completing |
/label lead-opted-in |
Apologies for any confusion, @liggitt. The box was left unchecked because the Just to clarify, when the KEP is targeting for I hope this clarifies any uncertainties. |
@sanchita-07 #4169 is merged, can you confirm this is tracked for 1.29? |
With KEP PR #4169 approved, the enhancement is ready for the enhancements freeze. The status is now marked as |
Hey there @seans3 👋, v1.29 Docs team shadow here. |
Hey there @seans3 👋, The deadline to open a placeholder PR against k/website for required documentation is Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you! |
Hello. Sorry for the delay. The placeholder PR for the docs for this enhancement is at: kubernetes/website#43620 Please let me know if there is anything else required. Thanks. |
Hey again @seans3 👋, 1.29 Enhancements team here. Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:
Are there additional code related PRs that need to be merged for 1.29? It looks like kubernetes/kubernetes#120889 is mentioned and needs to be included in the issue description. With all this, the status of this KEP is Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
@sanchita-07, #120889 is not targeting 1.29, only #119186 is (and that is now in the merge queue) |
Thanks @liggitt for mentioning :) With all the PRs related to the enhancement are linked in the above issue description and :
This enhancement is now |
Hi @seans3, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release. If so, you need to open a PR placeholder in the website repository. |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):WebSocket Client and V5 RemoteCommand Subprotocol kubernetes#119157
Stream Translator Proxy and FallbackExecutor for WebSockets kubernetes#119186
k/website
) update PR(s):Document Kubernetes' use of WebSockets (replacement for SPDY / KEP 4006) website#43620
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: