Prerequisites
- An OpenShift cluster, and
oc/kubectlaccess. - Helm 3.14 or later (Helm 4 works).
- The tracebloc CLI, signed in (
tracebloc login). It creates your secure environment’s Client ID and password; see Configuration → Authentication.
Install
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
Running, and on My Secure Environment your secure environment reads Active now under its name.
Environment-specific config
- OVN-Kubernetes enforces NetworkPolicy by default, so the training-pod egress lockdown works out of the box.
-
metrics-serveris present on OpenShift. -
GPU or CPU-only. In the
envblock ofvalues.yaml, declare what your nodes have. WithoutGPU_LIMITS, every training pod requests one NVIDIA GPU, and on CPU-only nodes it staysPending:The chart’svalues.yamlwritesenvin 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 (on OpenShift, usually through the NVIDIA GPU Operator), or let the chart run it:
Production notes
- The bundled SCC grants the resource-monitor the host access it needs — review it against your cluster policy.
- Size training compute per job; day-2 management is in Operations.