Cloudera Docs

Release notes

Learn about the new features, improvements, known and fixed issues, limitations, and unsupported features in this release of CSM Operator.

What's New

Learn about the new features and notable changes in this release of CSM Operator.

Rebase on Strimzi 0.41.0

This release of CSM Operator is based on Strimzi 0.41.0. For more information, see the Strimzi 0.41.0 Release Notes.

Kafka Connect support

You can now deploy Kafka Connect clusters and Kafka connectors using KafkaConnect and KafkaConnector resources. For more information, see Deploying Kafka Connect clusters .

Kafka replication support

You can now set up data replication between Kafka clusters using CSM Operator.

Replication of Kafka data is achieved by manually deploying Kafka Connect clusters and various replication connectors. This type replication setup is referred to as Kafka Connect-based replication. Kafka Connect-based replication does not involve the use of MirrorMaker 2 or the KafkaMirrorMaker2 resource shipped as part of Strimzi.

For more information, see Replication overview .

Fixed Issues

Learn what issues are fixed in this release of CSM Operator.

CSMDS-644: Kafka CLI commands fail with a TLS handshake error when using kafka_shell.sh
The kafka_shell.sh tool no longer fails with a TLS handshake error when an mTLS listener is configured for the Kafka cluster targeted by the tool.
CSMDS-721: Some alerts are triggered when deploying the prometheus-rules.yaml example
False positive results are no longer triggered when deploying the prometheus-rules.yaml example. The pod selector from the KafkaBrokerContainersDown rule is removed. The BridgeContainersDown,

EntityOperatorTlsSidecarContainerDown, and MirrorMakerContainerDown alerts are deleted.

Known Issues

Learn about the known issues in this release of CSM Operator.

CSMDS-334: ZooKeeper pods are running but Kafka pods are not created
Under certain circumstances, ZooKeeper pods might not be able to form a quorum. In a case like this, the creation of the Kafka cluster gets stuck in a state where ZooKeeper pods are running, but Kafka pods are not created.
If you encounter this issue, at least one of the ZooKeeper pods logs a WARN entry similar to the following: 
2024-02-23 18:45:00,311 WARN Unexpected exception (org.apache.zookeeper.server.quorum.QuorumPeer) [QuorumPeer[myid=3](plain=127.0.0.1:12181)(secure=[0:0:0:0:0:0:0:0]:2181)]
java.lang.InterruptedException: Timeout while waiting for epoch from quorum
	at org.apache.zookeeper.server.quorum.Leader.getEpochToPropose(Leader.java:1443)
	at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:606)
	at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1552)

This is caused by a race condition issue in ZooKeeper. ZooKeeper is unable to recover from this state automatically.

Delete the ZooKeeper pods that are unable to form a quorum.
kubectl delete pod [***ZOOKEEPER POD***] -n [***NAMESPACE***]

The Cluster Operator automatically recreates the ZooKeeper pods that are deleted. The newly created ZooKeeper pods are less likely to encounter the issue.

Unsupported features

Learn what features are unsupported in this release of CSM Operator.

The following Strimzi features are unsupported in CSM Operator:

  • Kafka MirrorMaker
  • Kafka MirrorMaker 2
  • Kafka Bridge
  • Kafka cluster creation without using KafkaNodePool resources