[Helm] Added additional configuration to values (#125)

- Added support for setting KUBERNETES_NODE_SELECTORS and KUBERNETES_TOLERATIONS for polytomic app
- Added nodeSelector and affinity support for vector

Author: erictg

CHANGELOG.md

@@ -8,8 +8,8 @@ This repository contains multiple deployment components, each with its own chang
 
 See [helm/charts/polytomic/CHANGELOG.md](helm/charts/polytomic/CHANGELOG.md)
 
-- **Current Version**: 1.2.0
-- **Latest Tag**: `polytomic-1.2.0`
+- **Current Version**: 1.2.1
+- **Latest Tag**: `polytomic-1.2.1`
 
 ### Terraform Modules
 

helm/charts/polytomic/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to the Polytomic Helm chart will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.2.1] - 2026-02-20
+
+### Added
+
+- **Kubernetes task executor scheduling options**: New `polytomic.kubernetes.nodeSelectors` and `polytomic.kubernetes.tolerations` values allow scheduling dynamically created task executor pods on specific nodes. These are passed to the application as `KUBERNETES_NODE_SELECTORS` and `KUBERNETES_TOLERATIONS` environment variables.
+
+- **Vector DaemonSet scheduling options**: New `polytomic.vector.daemonset.nodeSelector` and `polytomic.vector.daemonset.affinity` values allow scheduling Vector DaemonSet pods on specific nodes, complementing the existing `tolerations` option.
+
+| Value                                    | Default | Description                                                |
+| ---------------------------------------- | ------- | ---------------------------------------------------------- |
+| `polytomic.kubernetes.nodeSelectors`     | `""`    | Node selectors for task pods (format: `key=value,key=value`) |
+| `polytomic.kubernetes.tolerations`       | `""`    | Tolerations for task pods (format: `key:operator:value:effect`) |
+| `polytomic.vector.daemonset.nodeSelector`| `{}`    | Node selector for Vector DaemonSet pods                    |
+| `polytomic.vector.daemonset.affinity`    | `{}`    | Affinity rules for Vector DaemonSet pods                   |
+
+---
+
 ## [1.2.0] - 2026-02-19
 
 ### Added

helm/charts/polytomic/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.0.2
+version: 1.2.1
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

helm/charts/polytomic/README.md

@@ -143,6 +143,9 @@ Kubernetes: `>=1.34.0-0`
 | polytomic.field_change_tracking | bool | `true` |  |
 | polytomic.integrations | object | `{}` | Integration credentials Configure OAuth credentials and API keys for third-party integrations. Only non-empty values will be included in the deployment secret. Supports all integration environment variables in UPPER_CASE format.  Common integrations:   SALESFORCE_CLIENT_ID / SALESFORCE_CLIENT_SECRET   HUBSPOT_CLIENT_ID / HUBSPOT_CLIENT_SECRET   GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET / GITHUB_DEPLOY_KEY   SHOPIFY_CLIENT_ID / SHOPIFY_CLIENT_SECRET   STRIPE_SECRET_KEY   GOOGLEADS_CLIENT_ID / GOOGLEADS_CLIENT_SECRET / GOOGLEADS_DEVELOPER_TOKEN   GSHEETS_API_KEY / GSHEETS_APP_ID / GSHEETS_CLIENT_ID / GSHEETS_CLIENT_SECRET   And many more - see documentation for full list  Example:   integrations:     SALESFORCE_CLIENT_ID: "your-client-id"     SALESFORCE_CLIENT_SECRET: "your-client-secret"     HUBSPOT_CLIENT_ID: "your-hubspot-id"     HUBSPOT_CLIENT_SECRET: "your-hubspot-secret" |
 | polytomic.internal_execution_logs | bool | `false` |  |
+| polytomic.kubernetes | object | `{"nodeSelectors":"","tolerations":""}` | Kubernetes task executor scheduling configuration These settings control how Polytomic schedules dynamically created job pods |
+| polytomic.kubernetes.nodeSelectors | string | `""` | Node selectors for task executor pods (comma-separated key=value pairs) Format: key=value,key=value Example: "disktype=ssd,node-type=sync-worker" |
+| polytomic.kubernetes.tolerations | string | `""` | Tolerations for task executor pods (comma-separated) Format: key:operator:value:effect,key:operator:value:effect Example: "dedicated:Equal:sync-jobs:NoSchedule,gpu:Exists::NoSchedule" |
 | polytomic.log_level | string | `"info"` |  |
 | polytomic.metrics | bool | `false` | Telemetry |
 | polytomic.query_workers | int | `10` |  |
@@ -167,9 +170,11 @@ Kubernetes: `>=1.34.0-0`
 | polytomic.sync_workers | int | `10` |  |
 | polytomic.tracing | bool | `false` |  |
 | polytomic.tx_buffer_size | int | `1000` |  |
-| polytomic.vector.daemonset | object | `{"enabled":true,"image":"polytomic-vector","imagePullPolicy":"IfNotPresent","podLabelSelector":"vector.dev/include=true","resources":{"limits":{"cpu":"200m","memory":"256Mi"},"requests":{"cpu":"100m","memory":"128Mi"}},"serviceAccount":{"roleArn":""},"tag":"","tolerations":[]}` | Vector DaemonSet for stdout/stderr log collection Collects container logs from all Polytomic pods on each node Default: true (matches ECS behavior where polytomic_use_logger defaults to true) |
+| polytomic.vector.daemonset | object | `{"affinity":{},"enabled":true,"image":"polytomic-vector","imagePullPolicy":"IfNotPresent","nodeSelector":{},"podLabelSelector":"vector.dev/include=true","resources":{"limits":{"cpu":"200m","memory":"256Mi"},"requests":{"cpu":"100m","memory":"128Mi"}},"serviceAccount":{"roleArn":""},"tag":"","tolerations":[]}` | Vector DaemonSet for stdout/stderr log collection Collects container logs from all Polytomic pods on each node Default: true (matches ECS behavior where polytomic_use_logger defaults to true) |
+| polytomic.vector.daemonset.affinity | object | `{}` | Affinity rules for Vector DaemonSet pods |
 | polytomic.vector.daemonset.enabled | bool | `true` | Set to false to disable DaemonSet log collection Consider disabling for: - Development environments to save resources - Cost-sensitive deployments where only business logs are needed - When using alternative cluster-wide log collection - Security/compliance restrictions on DaemonSets |
 | polytomic.vector.daemonset.image | string | `"polytomic-vector"` | Image name for Vector DaemonSet (registry is set via imageRegistry). MUST use Polytomic's Vector image with ptconf for secret decryption. |
+| polytomic.vector.daemonset.nodeSelector | object | `{}` | Node selector for Vector DaemonSet pods |
 | polytomic.vector.daemonset.podLabelSelector | string | `"vector.dev/include=true"` | Label selector to filter which pods to collect logs from. Uses vector.dev/include=true which is set on all Polytomic pod templates, making collection independent of the Helm release name. |
 | polytomic.vector.daemonset.serviceAccount | object | `{"roleArn":""}` | ServiceAccount configuration for Vector DaemonSet |
 | polytomic.vector.daemonset.serviceAccount.roleArn | string | `""` | IAM role ARN for IRSA (EKS only) |

helm/charts/polytomic/templates/_helpers.tpl

@@ -377,6 +377,12 @@ KUBERNETES_SERVICE_ACCOUNT: {{ include "polytomic.serviceAccountName" . | quote
 {{- if .Values.imagePullSecrets }}
 KUBERNETES_IMAGE_PULL_SECRET: {{ (index .Values.imagePullSecrets 0).name | quote }}
 {{- end }}
+{{- if .Values.polytomic.kubernetes.nodeSelectors }}
+KUBERNETES_NODE_SELECTORS: {{ .Values.polytomic.kubernetes.nodeSelectors | quote }}
+{{- end }}
+{{- if .Values.polytomic.kubernetes.tolerations }}
+KUBERNETES_TOLERATIONS: {{ .Values.polytomic.kubernetes.tolerations | quote }}
+{{- end }}
 {{- /* Integration credentials - only output non-empty values */ -}}
 {{- range $key, $value := .Values.polytomic.integrations }}
 {{- if $value }}

helm/charts/polytomic/templates/vector-daemonset.yaml

@@ -107,6 +107,14 @@ spec:
         hostPath:
           path: /var/lib/vector
           type: DirectoryOrCreate
+      {{- with .Values.polytomic.vector.daemonset.nodeSelector }}
+      nodeSelector:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
+      {{- with .Values.polytomic.vector.daemonset.affinity }}
+      affinity:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
       {{- with .Values.polytomic.vector.daemonset.tolerations }}
       tolerations:
         {{- toYaml . | nindent 8 }}

helm/charts/polytomic/values.yaml

@@ -219,6 +219,18 @@ polytomic:
 
   internal_execution_logs: false
 
+  # -- Kubernetes task executor scheduling configuration
+  # These settings control how Polytomic schedules dynamically created job pods
+  kubernetes:
+    # -- Node selectors for task executor pods (comma-separated key=value pairs)
+    # Format: key=value,key=value
+    # Example: "disktype=ssd,node-type=sync-worker"
+    nodeSelectors: ""
+    # -- Tolerations for task executor pods (comma-separated)
+    # Format: key:operator:value:effect,key:operator:value:effect
+    # Example: "dedicated:Equal:sync-jobs:NoSchedule,gpu:Exists::NoSchedule"
+    tolerations: ""
+
   # Vector logging configuration
   vector:
     # -- Vector DaemonSet for stdout/stderr log collection
@@ -257,6 +269,10 @@ polytomic:
       # By default no tolerations are set, so Vector only runs on schedulable worker nodes.
       # Add tolerations here if your nodes have custom taints that Polytomic pods also tolerate.
       tolerations: []
+      # -- Node selector for Vector DaemonSet pods
+      nodeSelector: {}
+      # -- Affinity rules for Vector DaemonSet pods
+      affinity: {}
 
       # -- ServiceAccount configuration for Vector DaemonSet
       serviceAccount: