Cloudera Docs

Release notes

Learn about the new features, known and fixed issues, as well as deprecations and removals in this release of Cloudera Streams Messaging Operator for Kubernetes.

What's New

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

Rebase to Strimzi 0.49.1 and Kafka 4.1.1

This release of Cloudera Streams Messaging Operator for Kubernetes is based on Strimzi 0.49.1 (previously 0.47.0) and Kafka 4.1.1 (previously 4.0.1).

See the following upstream resources for more information on these versions:

Schema Registry

Schema Registry is a standalone application that allows you to efficiently store and manage schemas for your streaming data. It supports Avro and JSON schema formats, and provides schema evolution capabilities with configurable compatibility modes. Schema Registry helps ensure data consistency across your streaming applications by providing a central repository of schemas that applications use to validate their data. It provides a REST API and client libraries for programmatic access.

Schema Registry is a new component introduced in this release of Cloudera Streams Messaging Operator for Kubernetes. It is proprietary Cloudera software based on Cloudera Runtime.

See the following resources for more information:

Apache Iceberg Sink Connector for Kafka Connect

The Apache Iceberg Sink Connector is now certified for use with Cloudera Streams Messaging Operator for Kubernetes.

The connector must be installed from an external repository (for example, Maven Central) as it is not packaged or shipped by Cloudera.

See the following resources for more information:

New Brokers and Broker Details pages in Cloudera Surveyor for Apache Kafka

New Brokers and Broker Details pages are introduced in Cloudera Surveyor. The Brokers page displays all monitored brokers in a selected cluster, while individual Broker Details pages provide comprehensive information for each broker.

You can access these pages from the new Brokers menu item in the left navigation. The pages provide you with the following monitoring and management capabilities:

Brokers

  • View overall status, health, disk usage, alert information, and more for all brokers within a selected cluster.

  • Filter and sort brokers.

  • Navigate to any individual broker to open its Broker Details page.

Broker Details

  • View in-depth information about the status and health of an individual broker.

  • View all active alerts specific to the selected broker, with filtering and sorting capabilities.

  • View and edit broker configurations.

  • Access detailed information about log directories, including disk usage and replica distribution.

  • Track all topic partitions and replicas hosted on the broker.

Authentication keys are now generated automatically in Cloudera Surveyor

Authentication setup for Cloudera Surveyor is now simplified with automatic key generation. The surveyorConfig.surveyor.authentication.keys.active property now defaults to a cryptographically secure random 128-byte value when not explicitly configured. This eliminates the need to manually generate and configure a key when enabling authentication. For more information, see Authentication in Cloudera Surveyor for Apache Kafka.

Strimzi v1 API introduced for custom resources

The v1 API version is now available for all Strimzi Custom Resource Definitions (CRDs). This introduces a stable API for managing Kafka resources.

All example manifests in Cloudera documentation have been updated to use the v1 API version (kafka.strimzi.io/v1).

The v1alpha1, v1beta1, and v1beta2 API versions for Strimzi Custom Resources are deprecated and will be removed in a future release. Convert to the v1 API version (kafka.strimzi.io/v1) using the Strimzi v1 API Conversion Tool. For conversion instructions, see Converting Strimzi custom resources to the v1 API.

Fixed Issues

There are no fixed issues in this release.

Known Issues

There are no known issues in this release.

Deprecations

Learn what is deprecated in this release.

Strimzi

Mounting additional Secrets in the custom authentication type
Support for the spec.kafka.listeners[*].authentication.secrets property in the custom authentication type is deprecated and will be removed in a future release. Use the additional volumes and volume mounts instead to mount additional Secrets. For more information, see Configuring additional volumes and volume.
Storage overrides
Configuring storage overrides for persistent volumes is deprecated. The spec.storage.overrides property in the KafkaNodePool resource is now ignored. If you want to configure storage classes on a per-broker basis, deploy multiple KafkaNodePool resources with a different storage class each. You can find more details about migrating from storage overrides in Configuring Kafka storage with ZooKeeper | Strimzi
The type: oauth authentication in Kafka
The type: oauth authentication type is deprecated for both Kafka listeners (brokers) and clients (Kafka Connect) and will be removed in a future release. Use type: custom instead to configure OAuth authentication.
Strimzi API versions v1alpha1, v1beta1, and v1beta2
The v1alpha1, v1beta1, and v1beta2 API versions for Strimzi Custom Resources are deprecated and will be removed in a future release. Convert to the v1 API version (kafka.strimzi.io/v1) using the Strimzi v1 API Conversion Tool. For conversion instructions, see Converting Strimzi custom resources to the v1 API.

Kafka

None.

Cloudera Surveyor

None.

Schema Registry

None.

Removals

Learn what is removed in this release.

Strimzi

None.

Kafka

None.

Cloudera Surveyor

Target ports
The service.targetPort and service.tlsTargetPort properties are removed.

Schema Registry

None.

Behavioral changes

Learn about the behaviroal changes in this release.

Strimzi

None.

Kafka

None.

Cloudera Surveyor

Authentication keys used to generate authentication tokens are now generated automatically
Previous Behavior: The surveyorConfig.surveyor.authentication.keys.active property was not set by default. When configuring authentication, an authentication key of at least 32 bytes had to be generated manually.
New Behavior: The surveyorConfig.surveyor.authentication.keys.active property now defaults to a cryptographically secure random 128-byte value when the property is not explicitly configured and FIPS mode is disabled. When both authentication and FIPS mode are enabled, the key must still be generated and set manually.

Schema Registry

None.