KEP-4568: Resilient Watch Cache Initialization: Add feature gate docs

[jpbetz]

KEP: Resilient Watchcache Initialization

cc @wojtek-t I don't know if we need any docs for this feature, but I got pinged about getting a placeholder docs PR in place so I took the liberty of creating this. Feel free to comment or take it over.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tengqm for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	bd50149
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/667dbfb75ef83c00084704ae

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	bd50149
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/667dbfb79053650008d11f42
😎 Deploy Preview	https://deploy-preview-47002--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[chanieljdan]

Thanks @jpbetz!
Link to associated KEP: Resilient Watchcache Initialization

[dipesh-rawat]

/sig api-machinery

[wojtek-t]

@jpbetz - I don't think we need any other docs specifically for this change.

But we have a second feature gate - I opened #47063 to contain both.
We should either proceed with mine or you can rebase yours and I can close mine.

[Princesso]

Hello, @wojtek-t and @jpbetz, have you both decided on which of the PRs to go with?

[Princesso]

Hello, @wojtek-t and @jpbetz, have you both decided on which of the PRs to go with?

Hi @wojtek-t and @jpbetz have you decided on which to go forward with? That way, we can close one of them out.

[wojtek-t]

We will proceed with #47063

[chanieljdan]

Hi @wojtek-t and @jpbetz,

Reaching out from the Docs team, just checking in as we approach Docs Freeze on Tuesday July 30th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze.

Looks like we're deciding on which PR to go with, could you let us know which to move forward with? We can close the one that's not needed out.

Thank you!

Daniel

[wojtek-t]

/close

[k8s-ci-robot]

@wojtek-t: Closed this PR.

In response to this:

/close

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.