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

Resource limits / affinity for the builder pods #10

Open
Cryptophobia opened this issue Mar 20, 2018 · 0 comments
Open

Resource limits / affinity for the builder pods #10

Cryptophobia opened this issue Mar 20, 2018 · 0 comments

Comments

@Cryptophobia
Copy link
Member

From @miracle2k on July 19, 2017 0:13

  • In https://deis.com/docs/workflow/managing-workflow/tuning-component-settings/#setting-resource-limits it says I can use BUILDER_POD_NODE_SELECTOR to target specific nodes. How do I actually provide this environment variable. Can I set this through helm/values.yaml?

  • As far as I can tell, if I want a host that is exclusively responsible as a builder, I need to taint the node and assign tolerations to the builder pods; this is not supported yet though, or is it?

  • The limits_cpu and limits_memory settings I can apply to the "builder component"; but that is distinct from the builder pods, right? Is there a way to resource limit them.

I am asking this because I have had repeated trouble with the builders taking down other containers, I can only assume due to resource usage. My nodes are, admittedly, not the most powerful ones.

Copied from original issue: deis/workflow#840

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

1 participant