Skip to main content
When to pick it — You already run Kubernetes on-prem (k3s, kubeadm, RKE, …) and want a secure environment on it, with full control over scheduling and storage.

Prerequisites

  • A running Kubernetes cluster and kubectl access.
  • Helm 3.14 or later (Helm 4 works).
  • metrics-server installed. The chart refuses to install without it, because the resource monitor reads metrics.k8s.io. On kubeadm and other clusters with self-signed kubelet certificates, start metrics-server with --kubelet-insecure-tls. If you can’t install it, set resourceMonitor.enabled: false and the chart skips the resource monitor.
  • The tracebloc CLI, signed in (tracebloc login). It creates your secure environment’s Client ID and password; see Configuration → Authentication.

Install

Before the last command, copy the Client ID and password from tb.env into values.yaml (see Configuration → Authentication). The chart goes into the namespace tb.env names, with the release named after it: that is where tracebloc CLI commands on this machine look for your secure environment. Delete tb.env after the install.

Verify

Pods Running, and on My Secure Environment your secure environment reads Active now under its name.

Environment-specific config

On a single-node cluster, use hostPath-backed volumes:
hostPath means one node: the volumes are ReadWriteOnce directories on whichever node a pod lands on, so on a multi-node cluster, pods on different nodes see different data. For multi-node clusters, keep hostPath.enabled: false, set storageClass.create: false and set storageClass.name to a ReadWriteMany class (NFS, CephFS or similar).
  • GPU or CPU-only. In the env block of values.yaml, declare what your nodes have. Without GPU_LIMITS, every training pod requests one NVIDIA GPU, and on CPU-only nodes it stays Pending:
    The chart’s values.yaml writes env in braces (env: { … }), where a new line without a comma is a YAML error. Replace that whole block with the one above, and carry over any other keys you’ve set. With GPUs, use x86_64 nodes with an NVIDIA GPU of the Turing generation or newer (GPU support). The nodes also need the NVIDIA device plugin. Install it yourself, or let the chart run it:
  • NetworkPolicy (training-pod egress lockdown) only enforces if your CNI supports it — Calico, Cilium, or kube-router. Flannel alone does not enforce.

Production notes

  • Schedule MySQL and storage on reliable nodes; back up the data PVCs.
  • Size training compute per job via RESOURCE_REQUESTS / RESOURCE_LIMITS (Configuration).
  • Day-2 upgrades and rollbacks: see Operations.