pingcap · ti-chi-bot · Jan 7, 2026 · Jan 6, 2026 · Jan 7, 2026
diff --git a/en/cheat-sheet.md b/en/cheat-sheet.md
@@ -434,7 +434,7 @@ See [kubectl Cheat Sheet](https://kubernetes.io/docs/reference/kubectl/cheatshee
 {{< copyable "shell-regular" >}}
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 ### Update Helm repository

diff --git a/en/clinic-user-guide.md b/en/clinic-user-guide.md
@@ -38,7 +38,7 @@ Before deploying Diag, make sure the following items are installed on the cluste
 
 #### Install Helm
 
-To install Helm and configure the chart repository `https://charts.pingcap.org/` maintained by PingCAP, you can refer to the [Use Helm](tidb-toolkit.md#use-helm) document.
+To install Helm and configure the chart repository `https://charts.pingcap.com/` maintained by PingCAP, you can refer to the [Use Helm](tidb-toolkit.md#use-helm) document.
 
 > **Note:**
 >
@@ -261,7 +261,7 @@ If your cluster cannot access the Internet, you can deploy Diag using the offlin
     To download Diag chart files, you can use the following command:
 
     ```shell
-    wget http://charts.pingcap.org/diag-${chart_version}.tgz
+    wget http://charts.pingcap.com/diag-${chart_version}.tgz
     ```
 
     Copy `diag-${chart_version}.tgz` to the cluster and unpack it to the current directory.
@@ -699,4 +699,4 @@ The following introduces how to use PingCAP Clinic to perform a quick check on a
     - The first part is the basic information about the cluster.
     - The second part is the sampling information.
     - The third part is the diagnostic results, including potential configuration problems. For each configuration potential risk found, Diag provides a corresponding knowledge base link with detailed configuration suggestions.
-    - The last line is the file path of the result report and record.
+    - The last line is the file path of the result report and record.
diff --git a/en/deploy-tidb-from-kubernetes-gke.md b/en/deploy-tidb-from-kubernetes-gke.md
@@ -88,7 +88,7 @@ If you see `Ready` for all nodes, congratulations. You've set up your first Kube
 2. Add the PingCAP repository:
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
 ## Deploy TiDB Operator

diff --git a/en/deploy-tidb-operator.md b/en/deploy-tidb-operator.md
@@ -149,7 +149,7 @@ If your server cannot access the Internet, install TiDB Operator offline by the
     {{< copyable "shell-regular" >}}
 
     ```shell
-    wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
+    wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
     ```
 
     Copy the `tidb-operator-v1.3.10.tgz` file to the target server and extract it to the current directory:

diff --git a/en/get-started.md b/en/get-started.md
@@ -218,7 +218,7 @@ This section describes how to install TiDB Operator using [Helm 3](https://helm.
     {{< copyable "shell-regular" >}}
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
     <details>

diff --git a/en/migrate-to-helm3.md b/en/migrate-to-helm3.md
@@ -73,7 +73,7 @@ tidb-operator   1               Tue Jan  5 15:28:00 2021        DEPLOYED
 
     ```
     NAME    URL
-    pingcap https://charts.pingcap.org/
+    pingcap https://charts.pingcap.com/
     ```
 
 4. Migrate the releases from Helm 2 to Helm 3:

diff --git a/en/tidb-toolkit.md b/en/tidb-toolkit.md
@@ -182,12 +182,12 @@ Kubernetes applications are packed as charts in Helm. PingCAP provides the follo
 * `tidb-drainer`: used to deploy TiDB Drainer;
 * `tikv-importer`: used to deploy TiKV Importer.
 
-These charts are hosted in the Helm chart repository `https://charts.pingcap.org/` maintained by PingCAP. You can add this repository to your local server or computer using the following command:
+These charts are hosted in the Helm chart repository `https://charts.pingcap.com/` maintained by PingCAP. You can add this repository to your local server or computer using the following command:
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 Then you can search the chart provided by PingCAP using the following command:
@@ -267,9 +267,9 @@ Use the following command to download the chart file required for cluster instal
 {{< copyable "shell-regular" >}}
 
 ```shell
-wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
-wget http://charts.pingcap.org/tidb-drainer-v1.3.10.tgz
-wget http://charts.pingcap.org/tidb-lightning-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-drainer-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-lightning-v1.3.10.tgz
 ```
 
 Copy these chart files to the server and decompress them. You can use these charts to install the corresponding components by running the `helm install` command. Take `tidb-operator` as an example:

diff --git a/en/upgrade-tidb-operator.md b/en/upgrade-tidb-operator.md
@@ -7,6 +7,38 @@ summary: Learn how to perform online upgrade and offline upgrade to TiDB Operato
 
 This document describes how to upgrade TiDB Operator to a specific version. You can choose either [online upgrade](#online-upgrade) or [offline upgrade](#offline-upgrade).
 
+## Upgrade considerations
+
+Review the following items before you upgrade TiDB Operator.
+
+- Effective January 4, 2026, the TiDB Operator Helm chart repository domain changes from `charts.pingcap.org` to `charts.pingcap.com`. If you previously installed TiDB Operator from `charts.pingcap.org`, follow these steps to update your Helm repository configuration:
+
+    1. Remove the old Helm repository:
+
+        ```shell
+        helm repo remove pingcap
+        ```
+
+    2. Add the new Helm repository:
+
+        ```shell
+        helm repo add pingcap https://charts.pingcap.com/
+        ```
+
+    3. Update the Helm repository index:
+
+        ```shell
+        helm repo update pingcap
+        ```
+
+- If you use TiDB Operator v1.3.0-beta.1 or earlier to deploy a TiDB cluster across multiple Kubernetes clusters, upgrading TiDB Operator directly causes a rolling update and can result in an abnormal cluster state. To upgrade TiDB Operator from an earlier version to v1.3, perform the following steps:
+
+    1. Update the Custom Resource Definitions (CRDs).
+    2. In the `TidbCluster` specification, set `spec.acrossK8s` to `true`.
+    3. Upgrade TiDB Operator.
+
+- The Pod `ValidatingWebhook` and `MutatingWebhook` are deprecated. If you use TiDB Operator v1.2 or earlier with these webhooks enabled, upgrading to v1.3.0-beta.1 or later removes them. This removal does not affect TiDB cluster management or any running TiDB clusters.
+
 ## Online upgrade
 
 If your server has access to the internet, you can perform online upgrade by taking the following steps:
@@ -130,7 +162,7 @@ If your server cannot access the Internet, you can offline upgrade by taking the
         {{< copyable "shell-regular" >}}
 
         ```bash
-        wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
+        wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
         ```
 
     3. Download the Docker images required for the new TiDB Operator version:

diff --git a/zh/cheat-sheet.md b/zh/cheat-sheet.md
@@ -434,7 +434,7 @@ summary: 介绍管理 TiDB 集群的 Command Cheat Sheet。
 {{< copyable "shell-regular" >}}
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 ### 更新 Helm repository

diff --git a/zh/clinic-user-guide.md b/zh/clinic-user-guide.md
@@ -38,7 +38,7 @@ Diag 部署前，请确认以下软件需求：
 
 #### 安装 Helm
 
-参考[使用 Helm](tidb-toolkit.md#使用-helm) 文档安装 Helm 并配置 PingCAP 维护的 chart 仓库 `https://charts.pingcap.org/`。
+参考[使用 Helm](tidb-toolkit.md#使用-helm) 文档安装 Helm 并配置 PingCAP 维护的 chart 仓库 `https://charts.pingcap.com/`。
 
 > **注意：**
 >
@@ -269,7 +269,7 @@ Make sure diag-collector components are running:
     通过以下命令，下载 Diag chart 文件：
 
     ```shell
-    wget http://charts.pingcap.org/diag-${chart_version}.tgz
+    wget http://charts.pingcap.com/diag-${chart_version}.tgz
     ```
 
     将 `diag-${chart_version}.tgz` 文件拷贝到服务器上并解压到当前目录：

diff --git a/zh/deploy-tidb-from-kubernetes-gke.md b/zh/deploy-tidb-from-kubernetes-gke.md
@@ -85,7 +85,7 @@ kubectl get nodes
 2. 通过下面的命令添加仓库：
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
 ## 部署 TiDB Operator

diff --git a/zh/deploy-tidb-operator.md b/zh/deploy-tidb-operator.md
@@ -151,7 +151,7 @@ tidbmonitors.pingcap.com             2020-06-11T07:59:41Z
     {{< copyable "shell-regular" >}}
 
     ```shell
-    wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
+    wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
     ```
 
     将 `tidb-operator-v1.3.10.tgz` 文件拷贝到服务器上并解压到当前目录：

diff --git a/zh/get-started.md b/zh/get-started.md
@@ -227,7 +227,7 @@ customresourcedefinition.apiextensions.k8s.io/tidbclusterautoscalers.pingcap.com
     {{< copyable "shell-regular" >}}
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
     <details>

diff --git a/zh/migrate-to-helm3.md b/zh/migrate-to-helm3.md
@@ -73,7 +73,7 @@ tidb-operator   1               Tue Jan  5 15:28:00 2021        DEPLOYED
 
     ```
     NAME    URL
-    pingcap https://charts.pingcap.org/
+    pingcap https://charts.pingcap.com/
     ```
 
 4. 迁移 Helm 2 管理的 release 到 Helm 3。

diff --git a/zh/tidb-toolkit.md b/zh/tidb-toolkit.md
@@ -182,12 +182,12 @@ Kubernetes 应用在 Helm 中被打包为 chart。PingCAP 针对 Kubernetes 上
 * `tidb-drainer`：用于部署 TiDB Drainer；
 * `tikv-importer`：用于部署 TiKV Importer；
 
-这些 chart 都托管在 PingCAP 维护的 helm chart 仓库 `https://charts.pingcap.org/` 中，你可以通过下面的命令添加该仓库：
+这些 chart 都托管在 PingCAP 维护的 helm chart 仓库 `https://charts.pingcap.com/` 中，你可以通过下面的命令添加该仓库：
 
 {{< copyable "shell-regular" >}}
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 添加完成后，可以使用 `helm search` 搜索 PingCAP 提供的 chart：
@@ -265,9 +265,9 @@ helm uninstall ${release_name} -n ${namespace}
 {{< copyable "shell-regular" >}}
 
 ```shell
-wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
-wget http://charts.pingcap.org/tidb-drainer-v1.3.10.tgz
-wget http://charts.pingcap.org/tidb-lightning-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-drainer-v1.3.10.tgz
+wget http://charts.pingcap.com/tidb-lightning-v1.3.10.tgz
 ```
 
 将这些 chart 文件拷贝到服务器上并解压，可以通过 `helm install` 命令使用这些 chart 来安装相应组件，以 `tidb-operator` 为例：

diff --git a/zh/upgrade-tidb-operator.md b/zh/upgrade-tidb-operator.md
@@ -9,13 +9,35 @@ summary: 介绍如何升级 TiDB Operator。
 
 ## 升级注意事项
 
-1. 如果使用 v1.3.0-beta.1 及更早版本的 TiDB Operator 跨 Kubernetes 集群部署 TiDB 集群，直接升级 TiDB Operator 会导致集群滚动更新并进入异常状态。如果从更早版本升级 TiDB Operator 到 v1.3，你需要执行以下操作：
+升级 TiDB Operator 前，请查看以下事项。
+
+- 自 2026 年 1 月 4 日起，TiDB Operator 的 Helm chart 仓库域名从 `charts.pingcap.org` 变更为 `charts.pingcap.com`。如果你之前是从 `charts.pingcap.org` 安装 TiDB Operator，请按照以下步骤更新 Helm repo 配置：
+
+    1. 移除旧的 Helm repo：
+
+        ```shell
+        helm repo remove pingcap
+        ```
+
+    2. 添加新的 Helm repo：
+
+        ```shell
+        helm repo add pingcap https://charts.pingcap.com/
+        ```
+
+    3. 更新 Helm repo：
+
+        ```shell
+        helm repo update pingcap
+        ```
+
+- 如果使用 v1.3.0-beta.1 及更早版本的 TiDB Operator 跨 Kubernetes 集群部署 TiDB 集群，直接升级 TiDB Operator 会导致集群滚动更新并进入异常状态。如果从更早版本升级 TiDB Operator 到 v1.3，你需要执行以下操作：
 
     1. 更新 CRD。
     2. 修改 TidbCluster 定义将 `spec.acrossK8s` 字段设置为 `true`。
     3. 升级 TiDB Operator。
 
-2. 弃用 Pod `ValidatingWebhook` 和 `MutatingWebhook`。如果使用 v1.2 及更早版本的 TiDB Operator 在集群部署了 Webhook，并启用了 Pod `ValidatingWebhook` 和 `MutatingWebhook`，升级 TiDB Operator 到 v1.3.0-beta.1 及之后版本，Pod `ValidatingWebhook` 和 `MutatingWebhook` 被删除，但这不会对 TiDB 集群管理产生影响，也不会影响正在运行的 TiDB 集群。
+- 弃用 Pod `ValidatingWebhook` 和 `MutatingWebhook`。如果使用 v1.2 及更早版本的 TiDB Operator 在集群部署了 Webhook，并启用了 Pod `ValidatingWebhook` 和 `MutatingWebhook`，升级 TiDB Operator 到 v1.3.0-beta.1 及之后版本，Pod `ValidatingWebhook` 和 `MutatingWebhook` 会被删除，但这不会对 TiDB 集群管理产生影响，也不会影响正在运行的 TiDB 集群。
 
 ## 在线升级
 
@@ -144,7 +166,7 @@ summary: 介绍如何升级 TiDB Operator。
         {{< copyable "shell-regular" >}}
 
         ```shell
-        wget http://charts.pingcap.org/tidb-operator-v1.3.10.tgz
+        wget http://charts.pingcap.com/tidb-operator-v1.3.10.tgz
         ```
 
     3. 下载 TiDB Operator 升级所需的 Docker 镜像: