Manage runtimes
Settings → Runtimes (Admins; pick the project at the top: it changes which project the section shows, not the project you are in) adds Kubernetes namespaces and Docker hosts with Add runtime. Each runtime's More actions menu has:
- Edit — name, settings, credentials (write-only: leave a secret empty to keep it) and the default Debezium image. Changing where a runtime points needs its running pipelines paused first. Pipeline manifests refer to runtimes by name, so update them after a rename.
- Disable / Enable — disabling cordons the runtime: pipelines already on it keep running and
can still be paused, resumed, restarted and snapshotted, but nobody can create, move or deploy
pipelines onto it (a blocking
runtime_disabledcheck). Both are audited. - Delete — once no pipeline uses it (move or delete them first) and deleted pipelines finished cleaning up; their history stays. Deleting an agent runtime revokes its token.
On a Docker runtime, BeziSync downloads a Debezium image the host does not have yet in the
background: the pipeline shows Downloading the connector image… (or, when it replaces a
running connector, keeps streaming on the old version with a note) and starts once the download
finishes. Image download timeout (10 minutes to 2 hours, default 30 minutes) bounds one
download; a Docker agent takes it from BEZISYNC_AGENT_DOCKER_IMAGE_PULL_TIMEOUT (the install
command sets it). On Kubernetes the node downloads images; a failed attempt only fails the
pipeline once Kubernetes gives up retrying (ImagePullBackOff).
The image a pipeline runs is fixed when it is deployed: changing a runtime's (or the install's) default image never restarts running pipelines. They pick it up at their next deploy, which their pipeline page shows as "next deploy".