Debezium versions
Settings → Debezium versions (Admins) is the one list of Debezium Server images every project
picks from, with how many pipelines run each one per project (each count links to that project's
Pipelines list filtered to that version). The install default (BEZISYNC_DEBEZIUM_DEFAULT_IMAGE) is always listed;
add releases or your own builds (extra converters, SMTs or drivers) with a label and notes, make one
the default (it overrides the install default; "Use install default" goes back), deprecate or
remove images. The catalog is advice, not enforcement: pipelines on a deprecated or unlisted image
keep running and get a non-blocking debezium_image_deprecated / debezium_image_unlisted check.
A new default never restarts running pipelines: they show it as their next deploy.
Destinations the official images lack run their own Debezium Server build, pinned by digest:
Apache Iceberg pipelines run ghcr.io/memiiso/debezium-server-iceberg (built on Debezium 3.6,
amd64 only), whatever the runtime or catalog default; the Pipelines list shows it as "Iceberg sink
422 image_family). Point BEZISYNC_ICEBERG_IMAGE at a mirror for private registries. Preflight blocks
a runtime whose nodes are all another architecture and warns when only some are
(sink_image_platform).
Making an image the default (or going back to the install default) asks first and says how many live pipelines run the current default.
Upgrading is pipeline work, done by editors where pipelines live. The Pipelines list has a Debezium column and version filter; select pipelines and Change Debezium version… to move them to an offered version, any other image, or back to the default (pipelines that already follow the default are redeployed when it changed). A pipeline's flow strip shows the version it runs and why (chosen for this pipeline, the runtime's default, or the default) with a Change button. Change one first, watch it reach Healthy, then the rest. Each change is a new version, so rollback is deploying the previous one.