update MD by dispatch event pingcap/docs-tidb-operator release-1.5

Author: github-actions

markdown-pages/en/tidb-in-kubernetes/release-1.5/cheat-sheet.md

@@ -386,7 +386,7 @@ See [kubectl Cheat Sheet](https://kubernetes.io/docs/reference/kubectl/cheatshee
 
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 ### Update Helm repository

markdown-pages/en/tidb-in-kubernetes/release-1.5/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.

markdown-pages/en/tidb-in-kubernetes/release-1.5/deploy-br-federation.md

@@ -184,7 +184,7 @@ This section describes how to install the BR Federation using [Helm 3](https://h
 3. Add the PingCAP repository:
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
 4. Install the BR Federation:
@@ -211,7 +211,7 @@ This section describes how to install the BR Federation using [Helm 3](https://h
 3. Add the PingCAP repository:
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
 4. Get the `values.yaml` file of the desired `br-federation` chart for deployment.

markdown-pages/en/tidb-in-kubernetes/release-1.5/deploy-tidb-from-kubernetes-gke.md

@@ -91,7 +91,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

markdown-pages/en/tidb-in-kubernetes/release-1.5/deploy-tidb-operator.md

@@ -142,7 +142,7 @@ If your server cannot access the Internet, install TiDB Operator offline by the
 
     
     ```shell
-    wget http://charts.pingcap.org/tidb-operator-v1.5.5.tgz
+    wget http://charts.pingcap.com/tidb-operator-v1.5.5.tgz
     ```
 
     Copy the `tidb-operator-v1.5.5.tgz` file to the target server and extract it to the current directory:

markdown-pages/en/tidb-in-kubernetes/release-1.5/get-started.md

@@ -204,7 +204,7 @@ To install TiDB Operator, you can use [Helm 3](https://helm.sh/docs/intro/instal
 1. Add the PingCAP repository:
 
     ```shell
-    helm repo add pingcap https://charts.pingcap.org/
+    helm repo add pingcap https://charts.pingcap.com/
     ```
 
     <details>

markdown-pages/en/tidb-in-kubernetes/release-1.5/migrate-to-helm3.md

@@ -68,7 +68,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:

markdown-pages/en/tidb-in-kubernetes/release-1.5/tidb-toolkit.md

@@ -162,11 +162,11 @@ Kubernetes applications are packed as charts in Helm. PingCAP provides the follo
 * `tidb-operator`: used to deploy TiDB Operator;
 * `tidb-lightning`: used to import data into a TiDB cluster;
 
-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:
 
 
 ```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:
@@ -235,8 +235,8 @@ Use the following command to download the chart file required for cluster instal
 
 
 ```shell
-wget http://charts.pingcap.org/tidb-operator-v1.5.5.tgz
-wget http://charts.pingcap.org/tidb-lightning-v1.5.5.tgz
+wget http://charts.pingcap.com/tidb-operator-v1.5.5.tgz
+wget http://charts.pingcap.com/tidb-lightning-v1.5.5.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:

markdown-pages/en/tidb-in-kubernetes/release-1.5/upgrade-tidb-operator.md

@@ -8,6 +8,38 @@ aliases: ['/docs/tidb-in-kubernetes/dev/upgrade-tidb-operator/']
 
 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:
@@ -121,7 +153,7 @@ If your server cannot access the Internet, you can offline upgrade by taking the
 
 
         ```bash
-        wget http://charts.pingcap.org/tidb-operator-v1.5.5.tgz
+        wget http://charts.pingcap.com/tidb-operator-v1.5.5.tgz
         ```
 
     3. Download the Docker images required for the new TiDB Operator version:

markdown-pages/zh/tidb-in-kubernetes/release-1.5/cheat-sheet.md

@@ -386,7 +386,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/cheat-sheet/']
 
 
 ```shell
-helm repo add pingcap https://charts.pingcap.org/
+helm repo add pingcap https://charts.pingcap.com/
 ```
 
 ### 更新 Helm repository