-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Enable per-request Read/Write Deadline #4460
Comments
/sig api-machinery |
/label lead-opted-in |
Hello @tkashem 👋, 1.31 Enhancements team here. Just checking in as we approach enhancements freeze on on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting for stage Here’s where this enhancement currently stands:
Before the enhancement freeze, it would be appreciated if following nits could be addressed:
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
Hello @tkashem 👋, 1.31 Docs Lead here. |
Hi @tkashem 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
@tkashem , friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
Hey again @tkashem 👋, 1.31 Enhancements team here, Just checking in as we approach code freeze at at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. 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 (and we need to update the Issue description to include all the related PRs of this KEP): (Compiled the following list based on the mention of PR #4462 in the description. Please let me know if there are any PRs listed below that don't require tracking as part of this KEP)
Additionally, please let me know if there are any other PRs in k/k not listed above that we should track for this KEP, so that we can maintain accurate status. If you anticipate missing code freeze, you can file an exception request in advance. The status of this enhancement is marked as |
Hey again @tkashem 👋, 1.31 Enhancements team here, Just a quick friendly reminder as we approach code freeze in around two weeks time, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. The current status of this enhancement is marked as If you anticipate missing code freeze, you can file an exception request in advance. |
Hi @dipesh-rawat, this enhancement will miss 1.31, more work is needed to satisfy all of the alpha criteria. I would like to target 1.32 for alpha. |
@tkashem Thank you for confirming that this enhancement will be targeted for a future release. I will mark this as I noticed that one PR kubernetes/kubernetes#124730, which is related to this KEP, has been merged into k/k. Not sure if it needs reverting or if we’re good since all tests in the PR passed. I’ll involve @sreeram-venkitesh (v1.31 Enhancements Lead) to review and ensure everything mentioned above is okay. Additionally, he can assist in clearing milestones and labels. @sreeram-venkitesh, please take a look at this when you get the chance. |
@tkashem Thanks for pinging us about moving this KEP to the next release! I'll remove it from the milestone now. /milestone clear @dipesh-rawat I don't think we need to revert the PR that was already merged. I will confirm this though. |
Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32. /remove-label lead-opted-in |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Enhancement Description
k/enhancements
) update PR(s): KEP-4460: Enable per-request Read/Write deadline #4462k/k
) update PR(s):k/website
) update PR(s): WIP: Placeholder for 1.31 KEP-4460 docs. website#46858Please 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: