Skip to content
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

Closed
anton-johansson opened this issue Mar 15, 2019 · 3 comments
Closed

Node roles #139

anton-johansson opened this issue Mar 15, 2019 · 3 comments

Comments

@anton-johansson
Copy link

anton-johansson commented Mar 15, 2019

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 and nginx. The nginx 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 the nodeSelector property of the pods' deployment/statefulset/daemonset?

Or is there a way of configuring which nodes descheduler should look at?

@aveshagarwal
Copy link
Contributor

yes descheuler has a command line flag --node-selector to target only selected nodes.

@anton-johansson
Copy link
Author

anton-johansson commented Mar 15, 2019

Cool, I can see that here:
https://github.com/kubernetes-incubator/descheduler/blob/d73471327b6737a3c85b4edd6416b0df654ceaab/cmd/descheduler/app/options/options.go#L56-L57

Thanks!

Is there any "official" documentation for descheduler? Any webpage, wiki-page, or something similar? Or maybe it will be added to Kubernetes official docs whenever #132 is dealt with?

@aveshagarwal
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants