Deprecate & remove Kubelet RunOnce mode

[HirazawaUi]

Enhancement Description

• One-line enhancement description (can be used as a release note): deprecate & remove Kubelet RunOnce mode
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4580-deprecate-kubelet-runonce/README.md
• Discussion Link: Deprecate & remove Kubelet RunOnce mode kubernetes#124030
• Primary contact (assignee): @HirazawaUi
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • deprecate and remove Kubelet RunOnce mode #4581
    • KEP-4580: Update KEP status to implementable #4736
  • Code (k/k) update PR(s): Deprecate Kubelet RunOnce mode kubernetes#125649
  • Docs (k/website) update PR(s): [WIP] Document deprecation & likely future removal of kubelet RunOnce mode website#46934

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[HirazawaUi]

/sig node
/assign

[SergeyKanzhelev]

/label lead-opted-in
/milestone v1.31

[SergeyKanzhelev]

/stage alpha

[ArkaSaha30]

Hello @HirazawaUi 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024..

This enhancement is targeting stage alpha for v1.31 (correct me, if otherwise)

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 before the enhancements freeze.

For this KEP, we would need to update the following:

• Retitle and attach the PR in this KEP description for Alpha
• Update the KEP status as implementable once reviewed.
• PR needs to be reviewed and merged within the mentioned timeline.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[sreeram-venkitesh]

With #4581 merged, we can mark this KEP as tracked for enhancements freeze 🎉

[mbianchidev]

Hello there @HirazawaUi

👋 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. Or like in this case a deprecation & removal.

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.

[hacktivist123]

Hello @HirazawaUi 👋, 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 familiarised with the docs requirement for the release.

Thank you!

[ArkaSaha30]

Hey again @HirazawaUi 👋, 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:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Regarding this enhancement, it appears that there are currently no open pull requests in the k/k repository related to it.

For this KEP, we would need to do the following:

• Ensure all PRs to the Kubernetes repo related to your enhancement are linked in the above issue description (for tracking purposes).
• Ensure all PRs are prepared for merging (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as at risk for code freeze.

[ArkaSaha30]

Hey again @HirazawaUi 👋, 1.31 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in about 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.

The current status of this enhancement is marked as at risk for code freeze. A few requirements mentioned in the comment #4580 (comment) still need to be completed:

• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

If you anticipate missing code freeze, you can file an exception request in advance.

[HirazawaUi]

@ArkaSaha30 I'm pushing it forward, but we still have some issues that are unresolved.

[ArkaSaha30]

@ArkaSaha30 I'm pushing it forward, but we still have some issues that are unresolved.

Since we are very close to the Code Freeze_(02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.)_ I would request you to file an exception request if you anticipate it can make it to 1.31.

[sreeram-venkitesh]

I'm guessing kubernetes/kubernetes#125649 is the only PR that we need to track for this KEP. This PR has got an approval and is waiting for conflicts to be fixed.

@HirazawaUi: Please let us know if there is anything else.

[sreeram-venkitesh]

Hello @HirazawaUi 👋 v1.31 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.31 milestone. (Your PR kubernetes/kubernetes#125649 has a merge conflict).

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/milestone clear

[HirazawaUi]

/close
@sreeram-venkitesh Thank you for your support, but we will close this issue and will not move forward with it.

[k8s-ci-robot]

@HirazawaUi: Closing this issue.

In response to this:

/close
@sreeram-venkitesh Thank you for your support, but we will close this issue and will not move forward with it.

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.

[sreeram-venkitesh]

@HirazawaUi Do we not need this KEP for the deprecation? Should someone else take up this KEP for the next cycle?