Skip to main content
A pipeline step runs on one of three kinds of place: a cluster of your own, Ankra’s build cluster, or a CI playground that Ankra builds for you on Ankra Cloud. The steps of most runs run only on your own cluster, while their logs and results reach Ankra wherever they ran (What Ankra keeps about a run). Two fallbacks can move work off it, both are on until you turn them off, and this page explains when each one acts, what it costs, and how to keep every pipeline step in your own cluster.

Your own cluster

Every run starts by choosing one of your organisation’s clusters, in this order. The first that answers wins. A production cluster, or one whose purpose nobody confirmed, is never chosen by the last rule, even when it is the organisation’s only cluster. With no cluster at all, a push, pull request, tag or schedule starts no run and gets a check titled Choose a CI cluster for this organisation. A run started by hand still starts: its build steps can go to Ankra’s build cluster, and its other steps conclude with that reason instead of running. A repository can also send its runs to one cluster of its own, whatever the organisation’s settings say. Its next runs go there; runs already queued keep theirs:
In your cluster, steps run as Kubernetes Jobs in the cluster’s ankra-ci namespaces, on its CI node group if it has one. The cluster’s agent needs pipeline workers: each worker runs one step at a time. Your source is checked out, built and tested there. What it costs: the nodes your cluster already runs on. A step reserves the CPU and memory it asks for, so a busy hour needs room on those nodes, or a node group that can grow.

Ankra’s build cluster

A build step builds a container image. Three things stop a run’s own cluster from building one: the run has no cluster at all (a run started by hand, above), the cluster’s agent does not run pipeline steps, or the nodes confine the rootless image builder (AppArmor or seccomp, common on Ubuntu and k3s nodes), which a step reports as build_runtime_confined. When that happens, Ankra can build the image on its own build cluster instead. A build for a pull request from a fork never goes there.
  • Only the builder is confined. Only build moves. Every other step runs on your cluster as usual.
  • No cluster, or an agent that runs no pipeline steps. The run’s scan steps run on Ankra’s platform scanner, against the commit and the image, so the scanner receives your source too. Steps that need your cluster, such as your own tests, are refused. gate and publish are settled by Ankra as usual.
Both of these must hold:
  • The organisation’s build fallback is on. It is on until an owner or admin turns it off: Build on Ankra when your cluster cannot, under Build rules in Build & delivery → Builds and clusters. In the CLI it is --build-fallback platform_builders.
  • Ankra has enabled platform builds for the organisation. This is Ankra’s grant, not a setting you can change. It is on for every organisation unless Ankra turned it off for yours. ankra org ci-settings get shows it.
What the build cluster receives: the repository, the commit, a short-lived GitHub installation token to fetch it, the Dockerfile path, and the registry login the image is pushed with. The builder fetches the source at that commit, builds the image and pushes it. The step that ran there carries the notice Built on Ankra platform builders, with the reason and the command that brings the run back in your cluster. With the build fallback off, a build your cluster cannot run is refused with a message that says why, and no build or scan of that run goes to Ankra. What it costs: Ankra counts the minutes of each build on its build cluster as Ankra-hosted pipeline minutes. Steps on your own clusters are never counted.

A CI playground

A run whose largest step no node of your CI cluster can hold would wait until its time ran out. A cluster where a step recently could not be scheduled, or was killed at its memory limit, in the last seven days, counts as too small too. For those runs, Ankra moves the whole run to a CI playground: an Ankra Cloud cluster it builds for the run, with pipeline workers. While the run waits for it, its queue reason is waiting_for_ci_playground.
  • The cheapest arrangement wins. When the run’s largest step fits Ankra Cloud’s trial plan, the organisation’s own free trial playground takes it: one already running, or a new one for an account without a payment method that still has a trial. Otherwise, when the organisation’s Ankra Cloud account can pay, it gets a billed playground at the smallest Ankra Cloud plan whose node fits the run’s largest step. An account linked to an Ankra organisation usually pays only from the credit the organisation tops up, so a card alone may not be enough. When Ankra Cloud refuses the playground, for example an account with no payment method and no trial left, the run stays on your cluster.
  • One playground per organisation. Every run that needs one shares it and queues for room on it like on any CI cluster. It grows to a larger plan only for a single step it cannot hold, and only once no step is running on it, because a resize restarts its server.
  • A billed playground is removed when it goes idle. Once no run has used it for the organisation’s idle time, 5 minutes unless you change it, Ankra tears it down. A trial playground is left to its own expiry.
The whole run moves, so the source is checked out, built and tested on that Ankra Cloud cluster. What it costs: nothing for a trial playground. A billed playground is charged at its Ankra Cloud plan’s price for the time it exists, idle time included, and never more in a month than the plan’s monthly price. See Ankra Cloud clusters. With the CI playground off, a run that does not fit stays on your cluster: it waits, and concludes if no node can take its largest step. Lower the stage’s resources, or add a node group with bigger nodes.

Keep everything in your own cluster

Two organisation settings keep every pipeline step on your own clusters. An organisation owner or admin changes them.
On an older CLI, the API changes the same setting:
ankra org ci-settings set --playground-idle-minutes 30, or {"ci_playground_idle_minutes": 30} in the same API call, changes how long an idle billed playground is kept, from 0 to 1440 minutes. A value outside that range is refused; the API answers “CI playground idle time must be between 0 and 1440 minutes.” ankra org ci-settings get prints Build fallback and Platform builds enabled, and from CLI 0.78.0 CI playground and Playground idle time as well. GET https://platform.ankra.app/api/v1/org/ci-settings returns ci_build_fallback, ci_auto_playground and ci_playground_idle_minutes.

Builds outside a pipeline run

The two settings cover pipeline steps. Ankra can also build an application’s image on its build cluster outside a pipeline run, for example the first build when you create the application, or a pull request preview whose image is missing. Ankra starts those builds by itself only while the build fallback is on and the organisation has Ankra’s platform builds grant, which ankra org ci-settings get shows as Platform builds enabled. With the build fallback off it starts none of them. If your source may never be built outside your own infrastructure, turn both settings off before you create an application. A build someone starts on Ankra’s build cluster by name, with ankra application build start or ankra application ship with --ankra-build, still runs there.

What Ankra keeps about a run

Wherever a step runs, on your cluster, Ankra’s build cluster or a CI playground, Ankra keeps the same things about it: Ankra counts what it holds in the Ankra-managed default vault; nothing in a vault of your own is counted. Change the retention on Build & delivery → Builds and clusters, under How long to keep pipeline results.