Skip to content
This repository was archived by the owner on Nov 30, 2021. It is now read-only.
This repository was archived by the owner on Nov 30, 2021. It is now read-only.

Resource limits / affinity for the builder pods #840

@miracle2k

Description

@miracle2k
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions