You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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:
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):KEP-4781: Fix inconsistent container start and ready state after kubelet restart #4784k/k
) update PR(s):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
The text was updated successfully, but these errors were encountered: