Resilient Watchcache Initialization

[wojtek-t]

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 release target 1.31:
  • Stable release target (x.y):

• Beta

  • KEP (k/enhancements) update PR(s): KEP 4568: Resilient watchcache initialization #4557
  • Code (k/k) update PR(s): Implement ResilientWatchCacheInitialization kubernetes#124642

• Stable

  • KEP (k/enhancements) update PR(s):
    • Propose to move ResilientWatchCacheInitialization feature flag to GA #5350
    • Propose to enable WatchCacheInitializationPostStartHook in 1.36 by default #5744
  • Code (k/k) update PR(s):
    • Gradute ResilientWatchCacheInitialization to GA kubernetes#131979
    • Enable WatchCacheInitializationPostStartHook by default kubernetes#135777
    • Graduate WatchCacheInitializationPostStartHook to GA kubernetes#139452

/sig api-machinery
/sig scalability
/milestone v1.31

[wojtek-t]

/label lead-opted-in

[dipesh-rawat]

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 beta for 1.31 (correct me, if otherwise)
/stage beta

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP.

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 tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[chanieljdan]

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

[hailkomputer]

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!
Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

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 XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[chanieljdan]

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 👋,

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