Roadmap

Conduit works in the open and we're always looking for feedback from the community. Our roadmap is publicly available at GitHub on this project.

v0.21 release train

v0.21.0 shipped the first slice of the Kafka Connect migration story: a conduit migrate kafka-connect command with rules for Debezium Postgres, the S3 sink and MirrorMaker 2, and five certified connectors. It did not deliver the whole plan. No migrated pipeline resumes from imported offsets yet: every migration re-snapshots until v0.22.

Shipped in v0.21:

• conduit migrate kafka-connect — translates Kafka Connect connector configs into Conduit pipelines plus a compatibility report. Rules for Debezium Postgres, the S3 sink and MirrorMaker 2; other connector classes are reported as unsupported
• Certified connectors: Postgres CDC, MySQL CDC (beta), Elasticsearch, Kafka and S3. migrate emits only the Postgres, Kafka and S3 connectors
• Protocol v3 with lossless structured values
• Protobuf decode for Confluent Schema Registry
• Secrets at rest — ${VAR} references are stored as references and resolved at provision time
• Public connector quality tiers in the registry index
• The benchi regression gate, live in CI
• Acceptance suite v2

Planned for v0.22:

• migrate rules for Debezium MySQL, JDBC source/sink and the Elasticsearch/OpenSearch sink
• Debezium offset import for Postgres, so a migrated Postgres pipeline resumes without a re-snapshot
• conduit kc lint and conduit kc diff
• The default engine flip (arch-v2 becomes the only engine; the v1 engine is removed)

Not shipped in v0.21 and not yet scheduled:

• Debezium-compatible output for Postgres
• The processor batch API and the stateless declaration (designed; the implementation is open)
• Python connector SDK GA and a published Python distribution (the SDK is pre-alpha)
• Kafka-to-Kafka partition, header and timestamp preservation, and S3 sink format parity, through migrate
• OpenSearch certification

Still to come later: the SMT compatibility pack.

Need a connector

If you need support for a particular data store that doesn't exist on the Connector list, check out the list of requested source connectors and the list of requested destination connectors.

Give the issue a +1 if you really need that connector. The upvote will help the team understand demand for any particular connector. If you find that an issue hasn't been created for your data store, please create a new issue in the Conduit repo.

tip

If you have any questions, feel free to ask on GitHub Discussions.