Runners
A runner is a deployed container that executes one or more node templates by claiming tasks. The Runners page shows every runner type registered on the environment, how busy it is, and whether its pods are healthy. Open Workloads, then Runners (/admin/runners).
The runners table
Filters narrow the list to runners that are Enabled only, that Have warnings, or that Have pending tasks.
| Column | Meaning |
|---|---|
| Runner | The runner type name |
| Health | Whether its pods are running as expected |
| Ready / Desired | Running pods against the number the scheduler wants |
| CPU, Memory | Live usage across the runner’s pods |
| Pending | Tasks waiting for this runner to claim them |
| Claimed | Tasks in progress on this runner |
| Throughput | Tasks completed over a recent window |
Badges flag special runners:
- Disabled, from a feature that is switched off.
- System, hosted inside the platform rather than as a separate deployment.
- Manual, operator-managed, where the scheduler does not auto-scale the pods.
Using it
Read this page with Tasks. A runner with a rising Pending count but no Ready pods is not being scheduled, so its work backs up. Check the runner’s health here and its pods on the Cluster page. A runner is enabled or disabled by turning its feature on or off.
Related
Opens your browser's print dialog. Choose "Save as PDF" as the destination.