-
Notifications
You must be signed in to change notification settings - Fork 645
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
Node roles #139
Comments
yes descheuler has a command line flag |
Cool, I can see that here: Thanks! Is there any "official" documentation for |
https://github.com/kubernetes-incubator/descheduler/blob/master/README.md. |
In my understanding, some of the policies that
descheduler
uses to evict pods are based on nodes. Node utilization, for example. I have two different roles in my cluster,worker
andnginx
. Thenginx
role will only ever have three pods:flannel
(or whatever pod networking we use)filebeat
(gather logs)nginx-ingress-controller
(handle ingresses)Wouldn't descheduler always consider those nodes under-utilized? Or does
descheduler
respect thenodeSelector
property of the pods' deployment/statefulset/daemonset?Or is there a way of configuring which nodes
descheduler
should look at?The text was updated successfully, but these errors were encountered: