Closed kaykhan closed 1 hour ago
Related #1350
Related #1350
You can see i have multiple nodes in my cluster, is this the same problem?
I0517 08:31:19.463161 1 descheduler.go:120] "The cluster size is 0 or 1 meaning eviction causes service disruption or degradation. So aborting.."
E0517 08:31:19.463192 1 descheduler.go:430] the cluster size is 0 or 1
Indicates that's not the case. can you show the output of this?
kubectl get nodes -l geeiq/node-type=worker
/kind support /remove-kind bug
I0517 08:31:19.463161 1 descheduler.go:120] "The cluster size is 0 or 1 meaning eviction causes service disruption or degradation. So aborting.." E0517 08:31:19.463192 1 descheduler.go:430] the cluster size is 0 or 1
Indicates that's not the case. can you show the output of this?
kubectl get nodes -l geeiq/node-type=worker
ip-10-1-11-56.eu-west-2.compute.internal Ready <none> 12d v1.30.0-eks-036c24b
ip-10-1-33-176.eu-west-2.compute.internal Ready <none> 25d v1.30.0-eks-036c24b
I'm not facing this problem anymore, so im going to close this
What version of descheduler are you using?
descheduler version: 0.29.0
Does this issue reproduce with the latest release?
yes
Which descheduler CLI options are you using?
-
Please provide a copy of your descheduler policy config file
What k8s version are you using (
kubectl version
)?1.29 AWS EKS
kubectl version
Output-- What did you do?
--
What did you expect to see?
Pods to be running
What did you see instead?
Pods stuck in CrashLookBackOff
kubectl get nodes
kubectl logs -f pod/descheduler-ddcd5b7b8-g694d -n kube-system
Installed using helm + terraform https://artifacthub.io/packages/helm/descheduler/descheduler