-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Pods that have UnexpectedAdmissionError are not automatically removed. #124934
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/sig node |
pods in failed state, including |
@ffromani pods in the |
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. |
Alright, thanks! |
Background
I'm using the Smarter Device Manager to allow Kubernetes (K8s) containers access to devices available on nodes (for example, /dev/kvm). However, when the node restarts, it takes a while for the Smarter Device Manager to initialize, as a result, pods scheduled on such nodes requiring access to /dev/kvm error out with a status of
UnexpectedAdmissionError
and with the following error:Although, after a while, I see new pod pertaining to the job scheduled, the older pod still remains errored out and not removed.
Kubernetes version
Client Version: v1.26.9
Kustomize Version: v4.5.7
Server Version: v1.26.11
What did I expect to happen?
I expect that pods with status
UnexpectedAdmissionError
are removed automatically by Kubernetes.Steps to reproduce
OS
The text was updated successfully, but these errors were encountered: