Skip to content

Glossary

One word per concept. The rejected forms below are refused in CI, so this page and the linter can never disagree — they are generated from the same file.

The orchestrator: the service that holds the desired state, admits changes, and dispatches them to agents.

Not: CP.

See Architecture.

The orchestrated unit: a named declaration of an image, its replica count and everything that shapes how those containers run.

Not: workloads, workload.

See Deployments and containers.

A machine enrolled in the platform that can run containers.

Not: hosts, host.

See Architecture.

The isolation boundary. Every deployment, node, secret and network belongs to exactly one.

Not: customers, customer.

See Tenancy and isolation.

The arrangement, not the party: a tenant is the boundary, tenancy is the model it belongs to.

See Tenancy and isolation.

One running copy of a deployment’s image.

Not: instances, instance.

See Deployments and containers.

The software running on a node that receives dispatches from the control plane and drives the container runtime. A node is the machine; the agent is the program on it.

See Architecture.

How an existing deployment’s containers are replaced with a new revision.

See Deployments and containers.

Not this

This page defines the words, not the fields. Types, defaults and validation rules live in the generated reference.