From SSH Config to Running CDC Pipelines: Host-Based Deployment for Debezium Platform

Description and use

Debezium Platform now supports deploying CDC pipelines on VMs and on‑premise infrastructure via SSH config discovery, Ansible provisioning, and container management through Ansible or an HTTP Host Agent.

Problem

Teams using Debezium Platform on VMs or on‑premise infrastructure lacked a deployment path outside Kubernetes, limiting adoption.

Outcome

The platform now supports deploying CDC pipelines on VMs or on‑premise hosts using SSH config discovery, Ansible provisioning, and optional Host Agent for container lifecycle, without removing the existing Kubernetes operator path.

Workflow

• 1. Configure SSH hosts in ~/.ssh/config
• 2. Conductor’s SSH Config Watcher reconciles hosts with the database
• 3. HostProvisioningService triggers Ansible playbook to prepare host (install prerequisites, optional Host Agent, Docker setup)
• 4. HostPipelineController selects a ready host, allocates port, creates deployment state
• 5. Runtime (Ansible or Host Agent) deploys Debezium Server container
• 6. Conductor polls status until RUNNING
• 7. Subsequent lifecycle ops (start, stop, undeploy, logs) use chosen runtime

Evidence

The work is now merged upstream.

Source

Ansible remains the default runtime. Agent mode is explicitly selected when the Host Agent should handle container lifecycle operations through HTTP.