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: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4781-kublet-restart-pod-status/README.md

• 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 restarting kubelet does not change pod status #5493
  • Code (k/k) update PR(s): KEP-4781: Restarting kubelet does not change pod status kubernetes#134746
  • Docs (k/website) update PR(s): kep-4781: Add docs for ChangeContainerStatusOnKubeletRestart feature gate website#52876

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