Some check and discover pods are not being created on the correct nodepool. I would like to check which component in the values files should be modified to include the tolerations and affinities. I am currently using the helm version 1.5.1

For Helm chart V1 (which includes version 1.5.1), you need to configure node selectors, tolerations, and affinities for check and discover pods by setting job-specific environment variables. The key issue is that the generic

JOB_KUBE_NODE_SELECTORS

/

JOB_KUBE_TOLERATIONS

fallback does not reliably apply to non-sync jobs (check, discover, spec). You must set them explicitly. What to configure in your values.yaml You need to set the job-specific environment variables under the

workload-launcher

(or

worker

) component's

extraEnv

section:

workload-launcher:
  nodeSelector:
    type: static  # selector for the launcher pod itself
  extraEnv:
    - name: JOB_KUBE_NODE_SELECTORS
      value: "type=jobs"
    - name: SPEC_JOB_KUBE_NODE_SELECTORS
      value: "type=jobs"
    - name: CHECK_JOB_KUBE_NODE_SELECTORS
      value: "type=jobs"
    - name: DISCOVER_JOB_KUBE_NODE_SELECTORS
      value: "type=jobs"
    - name: JOB_KUBE_TOLERATIONS
      value: "key=your-key,operator=Equal,value=your-value,effect=NoSchedule"
    - name: CHECK_JOB_KUBE_TOLERATIONS
      value: "key=your-key,operator=Equal,value=your-value,effect=NoSchedule"
    - name: DISCOVER_JOB_KUBE_TOLERATIONS
      value: "key=your-key,operator=Equal,value=your-value,effect=NoSchedule"
    - name: SPEC_JOB_KUBE_TOLERATIONS
      value: "key=your-key,operator=Equal,value=your-value,effect=NoSchedule"

[Helm chart V2 upgrade guide; Jobs-specific config docs] Key points • Do not rely solely on

JOB_KUBE_NODE_SELECTORS

or

JOB_KUBE_TOLERATIONS

— there is a known bug where the fallback for these variables does not work for check, discover, and spec jobs. You must explicitly set

CHECK_JOB_KUBE_NODE_SELECTORS

,

DISCOVER_JOB_KUBE_NODE_SELECTORS

, and

SPEC_JOB_KUBE_NODE_SELECTORS

(and their toleration equivalents). [Node Selectors forum post] • The `nodeSelector`/`tolerations`/`affinity` fields on the

workload-launcher

component itself only affect the launcher pod, not the workload pods it spawns. The spawned pods (check, discover, spec, sync) are controlled via the environment variables above. • The

effect

field in tolerations must be specified — omitting it has been reported to cause the toleration to not be applied. [JOB_KUBE_TOLERATIONS forum post] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.