Pods that have UnexpectedAdmissionError are not automatically removed. about kubernetes HOT 6 CLOSED

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

from kubernetes.

I expect that pods with status UnexpectedAdmissionError are removed automatically by Kubernetes.

/sig node
for triage

from kubernetes.

pods in failed state, including UnexpectedAdmissionError aren't automatically cleaned up to enable users to learn the failure conditions (e.g. logs). In order to enable automatic safe cleanup we need to have clear well known errors, which will probably require a (minor) RFE.

from kubernetes.

@ffromani pods in the UnexepectedAdmissionError state actually do not have any logs but only the status that can be seen through the kubectl describe command. I do believe that enabling a automatic safe cleanup is a useful feature to have and would greatly help us. Do you suggest I raise a RFE for this?

from kubernetes.

@ffromani pods in the UnexepectedAdmissionError state actually do not have any logs but only the status that can be seen through the kubectl describe command. I do believe that enabling a automatic safe cleanup is a useful feature to have and would greatly help us. Do you suggest I raise a RFE for this?

The key in this case is Failed state, which UnexpectedAdmissionError is one of the reason for. I think the first step is to have a clear indentifiable error which can enable automatic cleanup later on. Not sure the base system should do this cleanup but a cleaning controller would then be pretty trivial to create.

from kubernetes.

Alright, thanks!

from kubernetes.