Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md #10215

Conversation

akshayamadhuri
Copy link

issue : #10214

@gkarthiks
Copy link

I like the crisp response, but there's a little detail that needs to be added I believe.

If the kubelet on a node is stopped, the pods on that nodes will not be terminated effective immediately. The containers will continue to run, but since the health probes are not executed and reporting via PLEG is not available for the api-server, the API Server reckons the node and pods are not healthy and marks it for termination. But can't do that as well, since the kublet is down even if the control plane marks pods on that node for termination, the deletions cannot be enforced since kubelet is not running

So if kubelet is down, the pods on that node will become unmanaged orphans that continue running though they are "deleted" from Kubernetes' perspective. They won't get cleaned up until the kubelet is revived or the node is drained/decommissioned or naturally the containers' process exits out of error or completed status.

@akshayamadhuri
Copy link
Author

@gkarthiks shall I add more content

@gkarthiks
Copy link

@akshayamadhuri I would suggest that, but upto maintainers

@bregman-arie
Copy link
Owner

@akshayamadhuri Feel free

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants