Version support for open source Kafka
Last updated: 2025-09-19 17:35:32
Apache Kafka has evolved through approximately 30 versions from 0.7.x to 3.3.x, which can be divided into four development stages: 0.x, 1.x, 2.x, and 3.x. Currently, TDMQ for CKafka provides commercial cloud-compatible versions for these four stages, covering the mainstream Kafka versions used by users.
CKafka continuously iterates features, fixes bugs, and addresses stability risks on the basis of the open-source version. While maintaining full compatibility with open source, it undergoes deep optimization for actual enterprise application scenarios, providing users with a more stable and reliable service experience for messages.
This document introduces the open-source version support mechanism of TDMQ for CKafka, including support status, lifecycle explanation, selection recommendation, capability difference, and version upgrade instructions.
Version Number Introduction
The CKafka version is expressed as x.y.z_va.b.c.
x.y.z means the compatible open-source Kafka version, as follows:
x major version: major update, may contain incompatible API changes.
y minor version: new features, backward compatible.
z means patch version: Bug fixes or minor optimizations, with no new features introduced.
a.b.c refers to the CKafka enhanced version provided by Broker.
For example, 2.8.1_v1.0.0 means the enhanced version based on open source Kafka 2.8.1. See Broker version upgrade record for specific version update details.
Open-Source Version Support Notes
Tencent Cloud CKafka is compatible with open-source Kafka. Higher versions are fully backward compatible with lower versions. The following is the compatibility note:
CKafka Version | Compatible Community Edition | Compatibility |
0.10.2 (discontinued) | ≤ 0.10.x | 100% |
1.1.1 (discontinued) | ≤ 1.1.x | 100% |
2.4.1 | ≤ 2.4.x | 100% |
2.8.1 (Recommended) | ≤ 2.8.x | 100% |
3.2.3 | ≤ 3.2.x | 100% |
Note:
About CKafka 2.4.1 version description:
When launching version 2.4, CKafka was developed based on the stable Apache Kafka community branch 2.4.1. The community later had a brief development branch 2.4.2, but after several fixes and merges, it was eventually decided to revoke version 2.4.2. To maintain consistency with the community edition, CKafka has adjusted the originally labeled version 2.4.2 to match the community version 2.4.1. Currently, the CKafka 2.4.1 product line is fully compatible with all features of the Apache Kafka community version 2.4.1.
Lifecycle Explanation of CKafka Version
CKafka, Message Queue is a standalone code branch independently maintained by Tencent Cloud, 100% compatible with the Kafka protocol, featuring high performance, high availability, high reliability, high elasticity, and high security. All its versions have a lifecycle independent of the open-source community, uniformly maintained and managed by the Tencent Cloud Message Queue team. To ensure business stability, plan your upgrade schedule according to the product lifecycle and upgrade to supported versions promptly.
CKafka Version | Lifecycle Stage | EOM Time | Estimated EOFS Date | Estimated EOS Date |
0.10.2 | EOM | March 6, 2024 | None | None |
1.1.1 | EOM | March 6, 2024 | None | None |
2.4.1(2.4.2) | GA | None | | |
2.8.2 | GA | | | |
3.2.3 | GA | | | |
Note:
EOM: End of Marketing, stop the sale of this version.
EOS: End of Service & Support, disable service for this version. After this date, no technical support will be provided for the software version.
CKafka Version Capability Difference Comparison
Project | Capability | 2.4.1 | 2.8.1 | 3.2.3 |
Product form | Elastic storage | × | Professional Edition support | × |
Isolation | Traffic throttling | Professional Edition support | | × |
Security | SASL authentication | Supports PLAIN and SCRAM mechanisms. | | Supports PLAIN mechanism |
| ACL policy | Supports CIDR configuration | | CIDR cannot be configured |
| SSL encryption | Professional Edition support | | × |
Monitoring | Cluster load metrics | × | Professional Edition support | |
CKafka Version Selection Recommendation
Use Cases | Selection Recommendation |
Self-built Kafka migrate to the cloud | Matching version available: Select a CKafka version that matches the major version of your self-built Kafka. For example, if your self-built Kafka is version 2.8.1, select CKafka version 2.8.1. No matching version available: Upward compatibility: Recommend selecting a higher version. For example, if your self-built version is 2.8.0, recommend using version 2.8.1; if your self-built version is 1.1.1, recommend using version 2.4.1 or higher (each Broker version has backward compatibility). Not recommended to downgrade: Avoid selecting an earlier version of CKafka when your self-built version is higher, to prevent risks of incompatibility. |
First-time use of Kafka | For version function differences, refer to CKafka Version Capability Difference. Unless otherwise needed, recommend choose CKafka v2.8.1 (stable feature, excellent compatibility). |
Upgrading CKafka Version
Minor Version Upgrade Instructions
CKafka supports minor version upgrade through the console. For specific operations, refer to Upgrading Instance Kernel Minor Version.
Major Version Upgrade Instructions
CKafka does not support major version upgrade through the console currently. Console upgrade capacity will be provided subsequently. If you need to upgrade instance kernel major version, see Migrate Cluster for relevant guidelines and perform metadata and message data migration via migration solution.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback