Fix inconsistent container ready state after kubelet restart

[pololowww]

Enhancement Description

• One-line enhancement description (can be used as a release note): Fix inconsistent container ready state after kubelet restart

• Kubernetes Enhancement Proposal: KEP-4781: Fix inconsistent container start and ready state after kubelet restart #4784

• Discussion Link: Fix unexpected change of container ready state when kubelet restart kubernetes#123982

• Primary contact (assignee): @LastNight1997 @chenk008 @pololowww

• Responsible SIGs:

  • /sig node

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):KEP-4781: Fix inconsistent container start and ready state after kubelet restart #4784
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

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

[HirazawaUi]

Is this a duplicate of #4761?

[songminglong]

I agree that when kubelet restarts, the container state should be kept consistent. Pulling in and out is detrimental to the application and is not conducive to kubelet upgrades. We fixed this situation ourselves

[kannon92]

Please update the description with your PR.

[kannon92]

Given the reviews on the KEP, I'm moving this to proposed for consideration. Please sign the CLA.

[pololowww]

Given the reviews on the KEP, I'm moving this to proposed for consideration. Please sign the CLA.

Thanks, signed already:)

[haircommander]

/assign @pololowww

[haircommander]

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

[dipesh-rawat]

Hello @pololowww 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

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

/stage alpha

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.32.
• 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 on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

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. Thank you!

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

[pololowww]

• 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 on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

@dipesh-rawat Many thanks for reminding me of the deadline, but i think that the KEP4781 is not merged yet.#4784
Could you please let me know what i should do to ensure everything is on track?

[dipesh-rawat]

Hi @pololowww 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #4781 (comment) that still need to be completed.

It looks like PR #4784 will address most of these issues. The PR #4784 needs to be merged before the enhancements freeze.

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

[tjons]

Hello 👋, v1.32 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in 1.32, 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!

[tjons]

/milestone clear