-
Notifications
You must be signed in to change notification settings - Fork 668
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 strategies don't work #1341
Comments
Hi @y0zg, are you seeing descheduler remove pods with other status codes besides @knelasevero @a7i @ingvagabund I don't remember exactly how we check pod eviction reasons/statuses. Did we have any updated docs on what exactly is covered? |
The problem that I don't see that descheduler removes pods at all. I tried to set lifetime to 60sec with frequent cronjob run. One more interesting fact , in log I see this warning while running 0.27 version on 1.27 k8s version
I tried to use descheduler 0.28 version and with it above compatibility warning isn't present below is helm template for configmap
|
The warning message about compatibility was addressed here which landed in v0.28.1 and v0.29.0 but not v0.27.x As far as your second question, Additionally, reason All of that to say that you may want to use Question for maintainers - we should either merge the two strategies and formally retire |
Similar request for merging strategies is in #1169. Worth extending it with |
Since I shared the config (for sure it might contain incorrect settings as I was testing various options), can you check what should be corrected in order to delete "failed" pods, i.e. pods with status: Much appreciate! |
I stumbled upon this as i want to cleanup some "Completed" Pods which are not owned by jobs.
descheduler:v0.29.0 anything else i can try? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
descheduler version: v0.27.1
helm chart version: 0.27.1
Does this issue reproduce with the latest release?
Haven't tested
Which descheduler CLI options are you using?
Please provide a copy of your descheduler policy config file
helm values file
What k8s version are you using (
kubectl version
)?k8s version: v1.27.8-eks-8cb36c9
I don't see that descheduler removes pods with status
Error
,ContainerStatusUnknown
,Completed
The text was updated successfully, but these errors were encountered: