TiDB Cloud Release Notes in 2025

This page lists the release notes of TiDB Cloud in 2025.

January 21, 2025

Console changes

January 14, 2025

General changes

January 2, 2025

General changes

  • Support creating TiDB node groups for TiDB Cloud Dedicated clusters to enhance resource management flexibility.

    For more information, see Overview of TiDB Node Group.

  • Support connecting TiDB Cloud Dedicated clusters to generic Kafka in AWS and Google Cloud through Private Connect (beta).

    Private Connect leverages Private Link or Private Service Connect technologies from cloud providers to enable changefeeds in the TiDB Cloud VPC to connect to Kafka in customers' VPCs using private IP addresses, as if those Kafkas were hosted directly within the TiDB Cloud VPC. This feature helps prevent VPC CIDR conflicts and meets security compliance requirements.

    Note that using this feature incurs additional Private Data Link costs.

    For more information, see Changefeed Sink to Apache Kafka.

  • Introduce additional configurable options for Kafka changefeeds:

    • Support using the Debezium protocol. Debezium is a tool for capturing database changes. It converts each captured database change into a message called an event, and sends these events to Kafka. For more information, see TiCDC Debezium Protocol.

    • Support defining a single partition dispatcher for all tables, or different partition dispatchers for different tables.

    • Introduce two new dispatcher types for the partition distribution of Kafka messages: timestamp and column value.

    For more information, see Sink to Apache Kafka.

  • Enhance roles in TiDB Cloud:

    • Introduce the Project Viewer and Organization Billing Viewer roles to enhance granular access control on TiDB Cloud.

    • Rename the following roles:

      • Organization Member to Organization Viewer
      • Organization Billing Admin to Organization Billing Manager
      • Organization Console Audit Admin to Organization Console Audit Manager

    For more information, see Identity Access Management.

  • Regional high availability (beta) for TiDB Cloud Serverless clusters.

    This feature is designed for workloads that require maximum infrastructure redundancy and business continuity. Key functions include:

    • Nodes are distributed across multiple availability zones to ensure high availability in the event of a zone failure.
    • Critical OLTP (Online Transactional Processing) components, such as PD and TiKV, are replicated across availability zones for redundancy.
    • Automatic failover minimizes service disruption during a primary zone failure.

    This feature is currently available only in the AWS Tokyo (ap-northeast-1) region and can be enabled only during cluster creation.

    For more information, see High Availability in TiDB Cloud Serverless.

  • Upgrade the default TiDB version of new TiDB Cloud Dedicated clusters from v8.1.1 to v8.1.2.

Console changes

Was this page helpful?