-
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
Resilient Watchcache Initialization #4568
Comments
/label lead-opted-in |
Hello @wojtek-t 👋, 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:
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 |
Hi @wojtek-t 👋, 1.31 Docs Shadow here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarized with the docs requirement for the release. Thank you! Daniel |
Hi @wojtek-t 👋 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 |
Hi @wojtek-t 👋, Just a reminder to open a placeholder PR against dev-1.31 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday June 27, 2024 18:00 PDT. Thanks, Daniel |
Hi @wojtek-t 👋, Just a reminder to open a placeholder PR against dev-1.31 branch in the k/website repo for this (steps available here) if it requires docs. The deadline for this is tomorrow at Thursday June 27, 2024 18:00 PDT. Thanks, Daniel |
@wojtek-t , 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 @wojtek-t 👋, 1.31 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Here's where this enhancement currently stands:
With all the implementation(code related) PRs merged as per the issue description: Additionally, please let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status. This enhancement is now marked as |
@dipesh-rawat - I just linked another PR for it - with the second one (already merged too), we're ready for code-freeze. |
@wojtek-t Thanks for informing about the other PR kubernetes/kubernetes#125483 related to this KEP. Could we also please add this PR in the issue description (here) for tracking purposes? |
Docs PR: kubernetes/website#47063 |
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 |
/remove-lifecycle rotten |
@wojtek-t @serathius Is there anything preventing this from graduating to GA in 1.33? Anyone willing to own graduating this? If so let me know and I'll add it to the v1.33 milestone. |
Is there any plan to progress this to stable in 1.33? Should sig-api-machinery opt-in to this for milestone v1.33? (cc @serathius) |
@wojtek-t is out, I don't have enough context to know how much work is left. Will try to take a look. |
I think there are two parts of KEPs that need considered separately:
|
Sorry, I was OOO last weeks. I will not get to it for 1.33 upstream, but here is what I would like to happen:
|
Enhancement Description
One-line enhancement description (can be used as a release note): Resilient WatchCache initialization
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/4568-resilient-watchcache-initialization
Discussion Link:
Primary contact (assignee): @wojtek-t
Responsible SIGs: sig-api-machinery, sig-scalability
Enhancement target (which target equals to which milestone):
Beta
k/enhancements
) update PR(s): KEP 4568: Resilient watchcache initialization #4557k/k
) update PR(s): Implement ResilientWatchCacheInitialization kubernetes#124642k/website
) update(s): KEP-4568: Resilient Watch Cache Initialization: Add feature gate docs website#47002/sig api-machinery
/sig scalability
/milestone v1.31
The text was updated successfully, but these errors were encountered: