#Release Notes

#v4.2.0

#New and Optimized Features

#Community Kafka 4.1.1 Support

• Added support for the community Kafka version 4.1.1.
• All new instances created with v4.2.x will use Kafka 4.1.1 by default.

#ZooKeeper Mode Removal

• ZooKeeper mode has been completely removed: v4.2.x only supports KRaft mode.
• This aligns with the upstream Kafka community direction where ZooKeeper mode is deprecated.
• Important: All existing instances must be migrated to KRaft mode before upgrading to v4.2.x. Use the v4.1.x operator for migration.

#Kubernetes Security Hardening

• Enhanced security configurations for Kubernetes deployments.
• Added security context constraints for better pod isolation.

#v4.1.0

#New and Optimized Features

#Kafka data transfer support

Supports data transfer configuration through the Data Services view, using MirrorMaker 2 to achieve:

• Supports viewing transfer status.
• Supports monitoring and alert metrics.
• Supports MirrorMaker 2 configuration and management.

#Kraft mode support

Supports the creation of KRaft mode instances (3.x versions only). Kraft mode will gradually replace ZooKeeper mode. A migration plan from ZooKeeper mode to Kraft mode is available.(migrate to kraft)

#v4.0.0

#New and Optimized Features

#Component-Platform Decoupling

Alauda Streaming Services for Kafka's lifecycle has been decoupled from platform's, which means when customer needs a certain feature or a bug fix, Kafka team can release immediately instead of waiting for the platform release together.

#Real-Time Logs on Component Details Page

The logs on Kafka details page have been replaced with real-time logs that update instantly, facilitating troubleshooting and issue analysis.

#External Access via LoadBalancer for Kafka

LoadBalancer access is now supported for Kafka. When creating an instance, users can choose to expose services externally through a LoadBalancer-type Service.

Compared to NodePort, LoadBalancer provides better high availability, performance, and supports standard port exposure. It is recommended to use the LoadBalancer method in production environments.

Limitations

When using LoadBalancer, ensure that the cluster has available external address pools. We recommend using MetalLB to create external address pools for the cluster.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.