Configuration

This page summarizes the most common configuration surfaces.

Helm Values

The platform chart configures:

• scheduler and controller replicas,
• image repositories, tags, and pull policy,
• imagePullSecrets,
• leader election,
• service accounts and RBAC,
• security contexts,
• metrics Services,
• optional ServiceMonitor,
• node selectors, tolerations, and affinity.

Render chart output before applying:

helm template kruntimes ./charts/kruntimes --namespace kruntimes-system

Contributor-only Make variables and chart validation commands are documented in the Development Guide and Testing Guide .

Runtime Capacity

Runtime capacity is declared on the Runtime CRD:

spec:
  capacity:
    resources:
      runs: 4
      gpu: 1

The controller copies declared static capacity to Runtime Pod annotations. The scheduler tracks fast-changing active usage from Run state.

Runtime Pod Template

Runtime Pod customization lives in Runtime.spec.template.

spec:
  template:
    spec:
      serviceAccountName: custom-runtime-sa
      nodeSelector:
        workload: kruntimes
      tolerations:
        - key: dedicated
          operator: Equal
          value: runtimes
          effect: NoSchedule

The controller reserves fields needed by kruntimes. Do not override the injected runtimed container or kruntimes-managed labels and annotations.

Artifact Stores

Artifacts are written below $KRUNTIME_ARTIFACTS_DIR by workloads and persisted through the Runtime artifact store.

Supported backends:

• filesystem/PVC,
• S3-compatible object storage.

Run status stores bounded metadata in status.artifactRefs, not full artifact contents.

Environment Variables Exposed to Runs

Benchmark Variables

See Performance Benchmarks .