Skip to content

Operator scheduling

Scheduling options are passed to the upstream chart through upstream for direct package use, or packages.eckOperator.values.upstream with the umbrella’s packageConfiguration.version: v1 interface. Use the ECK 3.5.0 chart values for supported options and Kubernetes node scheduling guidance for scheduling semantics instead of a duplicated values schema.

These settings schedule the operator pod, not its managed Elasticsearch or Kibana pods. Workload scheduling belongs in those workload custom resources. Return to the ECK Operator integration guide.

For example, these package values restrict the operator to workers already labeled node-type: operator:

upstream:
  nodeSelector:
    node-type: operator

Alternatively, use node affinity when more than one label value is acceptable:

upstream:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
          - matchExpressions:
              - key: node-type
                operator: In
                values:
                  - operator
                  - platform

Use one approach or deliberately combine them: node selectors and required affinity must both match when supplied together. Neither example creates node labels or tolerates taints. Verify eligible nodes, taints, capacity, and existing scheduling rules before applying an overlay; an unsatisfiable requirement leaves the operator Pending and prevents workload reconciliation. Affinity lists replace existing lists. Do not reuse old pod anti-affinity examples with a dont-schedule-with label unless the selected pods actually carry that label.