Skip to main content
Runners execute your workflows in your own infrastructure: a Kubernetes cluster, a Docker host or a Linux VM. They connect out to Bentra over HTTPS and poll for jobs. Nothing connects in to them. See Network requirements.

​
1. Create a pool and a token

In Bentra, open Settings → Runner Pools and create a pool (or use the default one). The pool page shows a runner token once, right after you create it. Copy it then: Bentra keeps only a hash. Workflows choose a pool in Settings → Execution. Runs without a pool go to the default pool.

​
2. Install

The pool page shows these commands with your host and token filled in.
Requires Helm 3+.
  • Raise deployment.replicas to run more always-on runners.
  • To autoscale with KEDA v2+, use --set deployment.enabled=false --set keda.enabled=true --set keda.maxReplicas=10 instead.
  • Pin image.tag to the same version as the chart when you upgrade:

​
3. Check it connected

The pool page lists the connected runners with their version and status, refreshed every 15 seconds. A runner older than the latest release shows Outdated.

​
Plan limits

Your plan sets how many runners can be connected at once, across all your pools together, and how many runner pools you can create. See Plans and limits.
  • Settings → Runner Pools shows meters for active runners and runner pools.
  • A runner that starts when you’re at the limit is refused jobs and keeps retrying. It gets a slot about 90 seconds after another runner stops.
  • At the pool limit, you can’t create another pool. Existing pools keep working if your plan changes.
  • On Team and Business, Bentra can add extra runners or pools to your account. See Billing.

​
Versions

  • Runners send their version with every call.
  • Bentra has a minimum supported runner version. Below it, every runner call is refused with 426 Upgrade Required, and the response includes the minimum and the latest versions. Above the minimum, older runners keep working and show as Outdated.
  • Breaking changes to the runner protocol are listed in the runner changelog. They raise the minimum version.
  • Upgrade runners to the latest release when you see Outdated: Helm upgrade, rerun the VM install script with the new version, or pull the new image.