Debezium Blog
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.
Hello everyone, Jakub here. You may have noticed that there wasn’t much happening around Debezium UI lately. This, however, would be only partially true. We own you an explanation in this regard, so please bear with me. Let’s start with the status of the current UI project. It became increasing clear that while UI for Debezium is an important part of our vision, developing a UI strictly tied to Kafka Connect is not the right...
With Debezium 2.3, we introduced a preview of a brand new Debezium Operator with the aim to provide seamless deployment of Debezium Server to Kubernetes (k8s) clusters. The Debezium 2.4.0.Final release brings the next step towards the full support of this component. With this release, we are happy to announce that Debezium Operator is now available in the OperatorHub catalog for Kubernetes as well as in the community operator catalog embedded in the OpenShift and OKD distributions. The operator remains in the incubation phase; however, the full support of this component is approaching fast.
