You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/clinic-user-guide.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Before deploying Diag, make sure the following items are installed on the cluste
38
38
39
39
#### Install Helm
40
40
41
-
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.
41
+
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.
42
42
43
43
> **Note:**
44
44
>
@@ -261,7 +261,7 @@ If your cluster cannot access the Internet, you can deploy Diag using the offlin
261
261
To download Diag chart files, you can use the following command:
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
699
699
- The first part is the basic information about the cluster.
700
700
- The second part is the sampling information.
701
701
- 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.
702
-
- The last line is the file path of the result report and record.
702
+
- The last line is the file path of the result report and record.
Copy file name to clipboardExpand all lines: en/tidb-toolkit.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -181,12 +181,12 @@ Kubernetes applications are packed as charts in Helm. PingCAP provides the follo
181
181
*`tidb-lightning`: used to import data into a TiDB cluster;
182
182
*`tidb-drainer`: used to deploy TiDB Drainer;
183
183
184
-
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:
184
+
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:
185
185
186
186
{{< copyable "shell-regular">}}
187
187
188
188
```shell
189
-
helm repo add pingcap https://charts.pingcap.org/
189
+
helm repo add pingcap https://charts.pingcap.com/
190
190
```
191
191
192
192
Then you can search the chart provided by PingCAP using the following command:
@@ -265,9 +265,9 @@ Use the following command to download the chart file required for cluster instal
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:
Copy file name to clipboardExpand all lines: en/upgrade-tidb-operator.md
+33-1Lines changed: 33 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,38 @@ summary: Learn how to perform online upgrade and offline upgrade to TiDB Operato
7
7
8
8
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).
9
9
10
+
## Upgrade considerations
11
+
12
+
Review the following items before you upgrade TiDB Operator.
13
+
14
+
- 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:
15
+
16
+
1. Remove the old Helm repository:
17
+
18
+
```shell
19
+
helm repo remove pingcap
20
+
```
21
+
22
+
2. Add the new Helm repository:
23
+
24
+
```shell
25
+
helm repo add pingcap https://charts.pingcap.com/
26
+
```
27
+
28
+
3. Update the Helm repository index:
29
+
30
+
```shell
31
+
helm repo update pingcap
32
+
```
33
+
34
+
- 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:
35
+
36
+
1. Update the Custom Resource Definitions (CRDs).
37
+
2. In the `TidbCluster` specification, set`spec.acrossK8s` to `true`.
38
+
3. Upgrade TiDB Operator.
39
+
40
+
- 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.
41
+
10
42
## Online upgrade
11
43
12
44
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
0 commit comments