Skip to main content
One run installed by hand as one helm release per component: one per trainer, one per inference engine, and one carrying the orchestration script.

Example 1: A Single Policy Run

Inside a miles workbench the cluster backend and the namespace are already set; name the run once:
Then install one component per command — identical but for --deploy-component and --deploy-instance-id, with primary last since installing it blocks until the run ends: These scripts import their shared address book as examples.…, so run them as modules from the repository root rather than by path:
When the run ends, the releases that carry no orchestration script are still up:

Example 2: A Run That Trains Several Policies

run_solver_verifier_gsm8k_split.py installs the multi_policy solver / verifier demo the same way: one release per policy trainer, one per policy’s engines, and the orchestration script last — five releases for two policies. Name this run once as well, so the example stands on its own: