Essential-HighAvailability-changed

[qiqi-power]

• Essential only support zonal high availability
• Private link does not support cross-region

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

Essential only support High availability: zonal; related doc changed

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

Hi @qiqi-power. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Code Review

This pull request updates the TiDB Cloud documentation to reflect that the Essential plan only supports zonal high availability and does not support cross-AZ failover. It also clarifies that Private Link does not support cross-region connectivity, recommending VPC peering for Premium instances instead. The review feedback suggests grammatical improvements, terminology consistency (using lowercase for 'zonal high availability'), and rephrasing to use the active voice and second person in accordance with the style guide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The phrase "offers Zonal High Availability: places all components..." is grammatically awkward. Additionally, "zonal high availability" should be in lowercase to maintain consistency with other parts of the documentation. Let's rephrase it for better clarity and flow.

Suggested change

	{{{ .essential }}} offers Zonal High Availability: places all components within the same availability zone, which results in lower network latency. For more information, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md).
	{{{ .essential }}} offers zonal high availability, which places all components within the same availability zone to reduce network latency. For more information, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md).

References

1. Use consistent terminology and lowercase for 'zonal high availability' as seen in other parts of the documentation. ^(link)

[gemini-code-assist]

Improve grammatical parallelism ("to ensure... and maximize...") and add the missing article ("in the data plane").

Suggested change

When you create a {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximizing availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation.

When you create a {{{ .premium }}} instance with regional high availability, critical OLTP (Online Transactional Processing) workload components, such as PD and TiKV, are deployed across multiple availability zones to ensure redundant replication and maximize availability. During normal operations, components like Gateway, TiDB, and TiFlash compute/write nodes are hosted in the primary availability zone. These components in the data plane offer infrastructure redundancy through virtual machine pools, which minimizes failover time and network latency due to colocation.

[gemini-code-assist]

According to the style guide, we should write in the second person ("you") and avoid passive phrasing like "it is recommended to use". Let's rephrase this to be more direct.

Suggested change

	> Private Link currently does not support cross-region connectivity. For cross-region connections, it is recommended to use VPC peering to establish a link (TiDB Cloud Premium only feature).
	> Private Link currently does not support cross-region connectivity. For cross-region connections, use VPC peering to establish a connection (available only for TiDB Cloud Premium).

References

1. Write in second person ('you') and avoid passive/indirect phrasing like 'it is recommended to'. ^(link)

[qiancai]

/ok-to-test

[ti-chi-bot]

@qqqdan: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.