Release Notes
TOC
v4.3.2New and Optimized FeaturesCommunity Kafka 4.2.0 SupportStrimzi Kafka Operator UpdateKafka Console FixesFixed IssuesSecurity Fixesv4.2.2New and Optimized FeaturesCommunity Kafka 4.1.2 SupportFixed IssuesSecurity Fixesv4.2.0New and Optimized FeaturesCommunity Kafka 4.1.1 SupportZooKeeper Mode RemovalKubernetes Security Hardeningv4.1.0New and Optimized FeaturesKafka data transfer supportKraft mode supportv4.0.0New and Optimized FeaturesComponent-Platform DecouplingReal-Time Logs on Component Details PageExternal Access via LoadBalancer for KafkaFixed IssuesKnown Issuesv4.3.2
New and Optimized Features
Community Kafka 4.2.0 Support
- Added support for the community Kafka version 4.2.0.
- New instances created with v4.3.2 use Kafka 4.2.0 by default.
- To support Kafka 4.2.0 in the v4.3.x release, Alauda Container Platform Data Services RDS Framework must be version 4.2.2 or later.
Strimzi Kafka Operator Update
- Updated the Strimzi Kafka Operator component to the v4.3.x line, based on upstream Strimzi 0.48.0.
- Updated operator defaults and Kafka images to Kafka 4.2.0.
- Updated the Kafka Bridge image tag to v4.1.3.
Kafka Console Fixes
- Updated the Kafka console image in the operator bundle.
- Removed the hard-coded Kafka 4.1 default version. New instances now use the current supported Kafka version from the installed component version.
- Improved Kafka version list handling by de-duplicating display versions and preserving the current instance version during updates.
- Fixed Kafka console icon asset packaging.
Fixed Issues
Security Fixes
- Updated Kafka runtime dependencies to address known vulnerabilities.
- Fixed known vulnerabilities in upstream Kafka dependencies.
v4.2.2
New and Optimized Features
Community Kafka 4.1.2 Support
- Added support for the community Kafka version 4.1.2.
- New instances created with v4.2.2 use Kafka 4.1.2 by default.
Fixed Issues
Security Fixes
- Updated the Kafka runtime to include upstream security fixes from Kafka 4.1.2.
- Fixed known vulnerabilities in upstream Kafka dependencies.
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.