Recently there were some changes around Debezium charts, so I’m here to explain what these changes are and the reason behind them. As you should be aware from our latest release announcement, we are going to release the first version of our Debezium Management Platform.

Debezium Management Platform aims to simplify the deployment of Debezium to various environments in a highly opinionated manner. To achieve this goal, the platform uses a data-centric view of Debezium components.

It is for us a normal evolution from Debezium Server. We have provided you with an operator to easily operate it in Kubernetes environments, and now we are providing a high-level abstraction to deploy your data pipelines leveraging the operator + Debezium Server. You can read more on the reasoning behind this new project in the Status of Debezium UI.

Until now, we published helm charts only for our Debezium Server Operator and, for those who already started to use it, you should know that we publish it on charts.debezium.io. For those of you with keen eyes, you should have noticed two things:

  • Another entry appeared: debezium-platform

  • The urls for the operator have changed.

This is because, since the charts grew from 1 to 2, we decided to unify our charts so that you can easily find them in a single place. This place is charts.debezium.io.

Until now, the operator charts were released through the debezium-operator-manifest repo that was used not only for generating the helm chart repo index but also to publish the chart artifact. Starting from now, our chart packages (Debezium operator and Debezium platform) will be published as GitHub release artifacts on their respective repositories and, as described before, the helm chart index will contain both chart releases.

Essentially, we have integrated the charts release into our Debezium release process, eliminating the manual steps done in the past with the operator chart release.

What does it change for you?

If you already used the helm repo, you can just run:

helm repo update

so your index will be updated, then if you run:

helm search repo debezium/ --versions --devel

you can see that debezium-platform has appeared in the index together with the debezium-operator.

If you want, for example, to install our Debezium Platform, you can run the following:

helm install debezium-platform debezium/debezium-platform --version 3.1.0-beta1 --set database.enabled=true --set domain.url=platform.debezium.io

If instead, you have never used Debezium Helm chart, and you want to start playing with the Debezium Operator or the Debezium Platform, add the repository with:

helm repo add debezium https://charts.debezium.io

Lastly, we have also started to publish our Helm charts as OCI artifacts to quay.io, in which case you can install our charts with the following command:

helm install debezium-platform --set database.enabled=true --set domain.url=platform.debezium.io --version 3.1.0-beta1 oci://quay.io/debezium-charts/debezium-platform

Practically nothing changes for you, but we wanted to share what changed under the hood.

As usual, any feedback is always welcomed.

Fiore Mario Vitale

Mario is a Senior Software Engineer at Red Hat. He lives in Italy.

   


About Debezium

Debezium is an open source distributed platform that turns your existing databases into event streams, so applications can see and respond almost instantly to each committed row-level change in the databases. Debezium is built on top of Kafka and provides Kafka Connect compatible connectors that monitor specific database management systems. Debezium records the history of data changes in Kafka logs, so your application can be stopped and restarted at any time and can easily consume all of the events it missed while it was not running, ensuring that all events are processed correctly and completely. Debezium is open source under the Apache License, Version 2.0.

Get involved

We hope you find Debezium interesting and useful, and want to give it a try. Follow us on Twitter @debezium, chat with us on Zulip, or join our mailing list to talk with the community. All of the code is open source on GitHub, so build the code locally and help us improve ours existing connectors and add even more connectors. If you find problems or have ideas how we can improve Debezium, please let us know or log an issue.