en,zh; bump tidb components and dm to v5.4.0 (#1636) (#1639)

en/access-dashboard.md

@@ -55,7 +55,7 @@ TiDB Dashboard is built in the PD component in TiDB 4.0 and later versions. You
     metadata:
       name: basic
     spec:
-      version: v5.3.0
+      version: v5.4.0
       timezone: UTC
       pvReclaimPolicy: Delete
       pd:

en/advanced-statefulset.md

@@ -78,7 +78,7 @@ kind: TidbCluster
 metadata:
   name: asts
 spec:
-  version: v5.3.0
+  version: v5.4.0
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -130,7 +130,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[1]'
   name: asts
 spec:
-  version: v5.3.0
+  version: v5.4.0
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -184,7 +184,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[]'
   name: asts
 spec:
-  version: v5.3.0
+  version: v5.4.0
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:

en/aggregate-multiple-cluster-monitor-data.md

@@ -168,7 +168,7 @@ spec:
     version: 7.5.11
   initializer:
     baseImage: registry.cn-beijing.aliyuncs.com/tidb/tidb-monitor-initializer
-    version: v5.3.0
+    version: v5.4.0
   reloader:
     baseImage: registry.cn-beijing.aliyuncs.com/tidb/tidb-monitor-reloader
     version: v1.0.1

en/backup-restore-overview.md

@@ -49,9 +49,9 @@ This section introduces the fields in the `Backup` CR.
 
     - When using BR for backup, you can specify the BR version in this field.
         - If the field is not specified or the value is empty, the `pingcap/br:${tikv_version}` image is used for backup by default.
-        - If the BR version is specified in this field, such as `.spec.toolImage: pingcap/br:v5.3.0`, the image of the specified version is used for backup.
+        - If the BR version is specified in this field, such as `.spec.toolImage: pingcap/br:v5.4.0`, the image of the specified version is used for backup.
         - If the BR version is not specified in the field, such as `.spec.toolImage: private/registry/br`, the `private/registry/br:${tikv_version}` image is used for backup.
-    - When using Dumpling for backup, you can specify the Dumpling version in this field. For example, `spec.toolImage: pingcap/dumpling:v5.3.0`. If not specified, the Dumpling version specified in `TOOLKIT_VERSION` of the [Backup Manager Dockerfile](https://github.com/pingcap/tidb-operator/blob/master/images/tidb-backup-manager/Dockerfile) is used for backup by default.
+    - When using Dumpling for backup, you can specify the Dumpling version in this field. For example, `spec.toolImage: pingcap/dumpling:v5.4.0`. If not specified, the Dumpling version specified in `TOOLKIT_VERSION` of the [Backup Manager Dockerfile](https://github.com/pingcap/tidb-operator/blob/master/images/tidb-backup-manager/Dockerfile) is used for backup by default.
     - TiDB Operator supports this configuration starting from v1.1.9.
 * `.spec.tikvGCLifeTime`: The temporary `tikv_gc_life_time` time setting during the backup, which defaults to 72h.
 
@@ -233,8 +233,8 @@ This section introduces the fields in the `Restore` CR.
 
 * `.spec.metadata.namespace`: The namespace where the `Restore` CR is located.
 * `.spec.toolImage`：The tools image used by `Restore`.
-    - When using BR for restoring, you can specify the BR version in this field. For example,`spec.toolImage: pingcap/br:v5.3.0`. If not specified, `pingcap/br:${tikv_version}` is used for restoring by default.
-    - When using Lightning for restoring, you can specify the Lightning version in this field. For example, `spec.toolImage: pingcap/lightning:v5.3.0`. If not specified, the Lightning version specified in `TOOLKIT_VERSION` of the [Backup Manager Dockerfile](https://github.com/pingcap/tidb-operator/blob/master/images/tidb-backup-manager/Dockerfile) is used for restoring by default.
+    - When using BR for restoring, you can specify the BR version in this field. For example,`spec.toolImage: pingcap/br:v5.4.0`. If not specified, `pingcap/br:${tikv_version}` is used for restoring by default.
+    - When using Lightning for restoring, you can specify the Lightning version in this field. For example, `spec.toolImage: pingcap/lightning:v5.4.0`. If not specified, the Lightning version specified in `TOOLKIT_VERSION` of the [Backup Manager Dockerfile](https://github.com/pingcap/tidb-operator/blob/master/images/tidb-backup-manager/Dockerfile) is used for restoring by default.
     - TiDB Operator supports this configuration starting from v1.1.9.
 * `.spec.to.host`: The address of the TiDB cluster to be restored.
 * `.spec.to.port`: The port of the TiDB cluster to be restored.

en/configure-a-tidb-cluster.md

@@ -40,11 +40,11 @@ Usually, components in a cluster are in the same version. It is recommended to c
 
 Here are the formats of the parameters:
 
-- `spec.version`: the format is `imageTag`, such as `v5.3.0`
+- `spec.version`: the format is `imageTag`, such as `v5.4.0`
 
 - `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.baseImage`: the format is `imageName`, such as `pingcap/tidb`
 
-- `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`: the format is `imageTag`, such as `v5.3.0`
+- `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`: the format is `imageTag`, such as `v5.4.0`
 
 ### Recommended configuration
 

en/deploy-cluster-on-arm64.md

@@ -34,7 +34,7 @@ metadata:
   name: ${cluster_name}
   namespace: ${cluster_namespace}
 spec:
-  version: "v5.3.0"
+  version: "v5.4.0"
   # ...
   helper:
     image: busybox:1.33.0
@@ -87,7 +87,7 @@ spec:
   # ...
   initializer:
     baseImage: pingcap/tidb-monitor-initializer-arm64
-    version: v5.3.0
+    version: v5.4.0
   reloader:
     baseImage: pingcap/tidb-monitor-reloader-arm64
     version: v1.0.1

en/deploy-heterogeneous-tidb-cluster.md

@@ -28,7 +28,7 @@ metadata:
   name: ${heterogeneous_cluster_name}
 spec:
   configUpdateStrategy: RollingUpdate
-  version: v5.3.0
+  version: v5.4.0
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}
@@ -93,7 +93,7 @@ spec:
     version: 6.1.6
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.3.0
+    version: v5.4.0
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -134,7 +134,7 @@ spec:
   tlsCluster:
     enabled: true
   configUpdateStrategy: RollingUpdate
-  version: v5.3.0
+  version: v5.4.0
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}

en/deploy-on-general-kubernetes.md

@@ -41,17 +41,17 @@ This document describes how to deploy a TiDB cluster in general Kubernetes.
 
     If the server does not have an external network, you need to download the Docker image used by the TiDB cluster on a machine with Internet access and upload it to the server, and then use `docker load` to install the Docker image on the server.
 
-    To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v5.3.0):
+    To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v5.4.0):
 
     ```shell
-    pingcap/pd:v5.3.0
-    pingcap/tikv:v5.3.0
-    pingcap/tidb:v5.3.0
-    pingcap/tidb-binlog:v5.3.0
-    pingcap/ticdc:v5.3.0
-    pingcap/tiflash:v5.3.0
+    pingcap/pd:v5.4.0
+    pingcap/tikv:v5.4.0
+    pingcap/tidb:v5.4.0
+    pingcap/tidb-binlog:v5.4.0
+    pingcap/ticdc:v5.4.0
+    pingcap/tiflash:v5.4.0
     pingcap/tidb-monitor-reloader:v1.0.1
-    pingcap/tidb-monitor-initializer:v5.3.0
+    pingcap/tidb-monitor-initializer:v5.4.0
     grafana/grafana:6.0.1
     prom/prometheus:v2.18.1
     busybox:1.26.2
@@ -62,26 +62,26 @@ This document describes how to deploy a TiDB cluster in general Kubernetes.
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker pull pingcap/pd:v5.3.0
-    docker pull pingcap/tikv:v5.3.0
-    docker pull pingcap/tidb:v5.3.0
-    docker pull pingcap/tidb-binlog:v5.3.0
-    docker pull pingcap/ticdc:v5.3.0
-    docker pull pingcap/tiflash:v5.3.0
+    docker pull pingcap/pd:v5.4.0
+    docker pull pingcap/tikv:v5.4.0
+    docker pull pingcap/tidb:v5.4.0
+    docker pull pingcap/tidb-binlog:v5.4.0
+    docker pull pingcap/ticdc:v5.4.0
+    docker pull pingcap/tiflash:v5.4.0
     docker pull pingcap/tidb-monitor-reloader:v1.0.1
-    docker pull pingcap/tidb-monitor-initializer:v5.3.0
+    docker pull pingcap/tidb-monitor-initializer:v5.4.0
     docker pull grafana/grafana:6.0.1
     docker pull prom/prometheus:v2.18.1
     docker pull busybox:1.26.2
 
-    docker save -o pd-v5.3.0.tar pingcap/pd:v5.3.0
-    docker save -o tikv-v5.3.0.tar pingcap/tikv:v5.3.0
-    docker save -o tidb-v5.3.0.tar pingcap/tidb:v5.3.0
-    docker save -o tidb-binlog-v5.3.0.tar pingcap/tidb-binlog:v5.3.0
-    docker save -o ticdc-v5.3.0.tar pingcap/ticdc:v5.3.0
-    docker save -o tiflash-v5.3.0.tar pingcap/tiflash:v5.3.0
+    docker save -o pd-v5.4.0.tar pingcap/pd:v5.4.0
+    docker save -o tikv-v5.4.0.tar pingcap/tikv:v5.4.0
+    docker save -o tidb-v5.4.0.tar pingcap/tidb:v5.4.0
+    docker save -o tidb-binlog-v5.4.0.tar pingcap/tidb-binlog:v5.4.0
+    docker save -o ticdc-v5.4.0.tar pingcap/ticdc:v5.4.0
+    docker save -o tiflash-v5.4.0.tar pingcap/tiflash:v5.4.0
     docker save -o tidb-monitor-reloader-v1.0.1.tar pingcap/tidb-monitor-reloader:v1.0.1
-    docker save -o tidb-monitor-initializer-v5.3.0.tar pingcap/tidb-monitor-initializer:v5.3.0
+    docker save -o tidb-monitor-initializer-v5.4.0.tar pingcap/tidb-monitor-initializer:v5.4.0
     docker save -o grafana-6.0.1.tar grafana/grafana:6.0.1
     docker save -o prometheus-v2.18.1.tar prom/prometheus:v2.18.1
     docker save -o busybox-1.26.2.tar busybox:1.26.2
@@ -92,14 +92,14 @@ This document describes how to deploy a TiDB cluster in general Kubernetes.
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker load -i pd-v5.3.0.tar
-    docker load -i tikv-v5.3.0.tar
-    docker load -i tidb-v5.3.0.tar
-    docker load -i tidb-binlog-v5.3.0.tar
-    docker load -i ticdc-v5.3.0.tar
-    docker load -i tiflash-v5.3.0.tar
+    docker load -i pd-v5.4.0.tar
+    docker load -i tikv-v5.4.0.tar
+    docker load -i tidb-v5.4.0.tar
+    docker load -i tidb-binlog-v5.4.0.tar
+    docker load -i ticdc-v5.4.0.tar
+    docker load -i tiflash-v5.4.0.tar
     docker load -i tidb-monitor-reloader-v1.0.1.tar
-    docker load -i tidb-monitor-initializer-v5.3.0.tar
+    docker load -i tidb-monitor-initializer-v5.4.0.tar
     docker load -i grafana-6.0.1.tar
     docker load -i prometheus-v2.18.1.tar
     docker load -i busybox-1.26.2.tar

en/deploy-tidb-binlog.md

@@ -27,7 +27,7 @@ TiDB Binlog is disabled in the TiDB cluster by default. To create a TiDB cluster
       ...
       pump:
         baseImage: pingcap/tidb-binlog
-        version: v5.3.0
+        version: v5.4.0
         replicas: 1
         storageClassName: local-storage
         requests:
@@ -46,7 +46,7 @@ TiDB Binlog is disabled in the TiDB cluster by default. To create a TiDB cluster
       ...
       pump:
         baseImage: pingcap/tidb-binlog
-        version: v5.3.0
+        version: v5.4.0
         replicas: 1
         storageClassName: local-storage
         requests:
@@ -197,7 +197,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust
 
     ```yaml
     clusterName: example-tidb
-    clusterVersion: v5.3.0
+    clusterVersion: v5.4.0
     baseImage:pingcap/tidb-binlog
     storageClassName: local-storage
     storage: 10Gi
@@ -230,7 +230,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust
 
     ```yaml
     ...
-    clusterVersion: v5.3.0
+    clusterVersion: v5.4.0
     baseImage: pingcap/tidb-binlog-enterprise
     ...
     ```

en/deploy-tidb-dm.md

@@ -29,9 +29,9 @@ Usually, components in a cluster are in the same version. It is recommended to c
 
 The formats of the related parameters are as follows:
 
-- `spec.version`: the format is `imageTag`, such as `v5.3.0`.
+- `spec.version`: the format is `imageTag`, such as `v5.4.0`.
 - `spec.<master/worker>.baseImage`: the format is `imageName`, such as `pingcap/dm`.
-- `spec.<master/worker>.version`: the format is `imageTag`, such as `v5.3.0`.
+- `spec.<master/worker>.version`: the format is `imageTag`, such as `v5.4.0`.
 
 TiDB Operator only supports deploying DM 2.0 and later versions.
 
@@ -50,7 +50,7 @@ metadata:
   name: ${dm_cluster_name}
   namespace: ${namespace}
 spec:
-  version: v5.3.0
+  version: v5.4.0
   configUpdateStrategy: RollingUpdate
   pvReclaimPolicy: Retain
   discovery: {}
@@ -141,27 +141,27 @@ kubectl apply -f ${dm_cluster_name}.yaml -n ${namespace}
 
 If the server does not have an external network, you need to download the Docker image used by the DM cluster and upload the image to the server, and then execute `docker load` to install the Docker image on the server:
 
-1. Deploy a DM cluster requires the following Docker image (assuming the version of the DM cluster is v5.3.0):
+1. Deploy a DM cluster requires the following Docker image (assuming the version of the DM cluster is v5.4.0):
 
     ```shell
-    pingcap/dm:v5.3.0
+    pingcap/dm:v5.4.0
     ```
 
 2. To download the image, execute the following command:
 
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker pull pingcap/dm:v5.3.0
-    docker save -o dm-v5.3.0.tar pingcap/dm:v5.3.0
+    docker pull pingcap/dm:v5.4.0
+    docker save -o dm-v5.4.0.tar pingcap/dm:v5.4.0
     ```
 
 3. Upload the Docker image to the server, and execute `docker load` to install the image on the server:
 
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker load -i dm-v5.3.0.tar
+    docker load -i dm-v5.4.0.tar
     ```
 
 After deploying the DM cluster, execute the following command to view the Pod status:

en/deploy-tidb-enterprise-edition.md

@@ -21,7 +21,7 @@ Currently, the difference between the deployment of TiDB Operator Enterprise Edi
 
 ```yaml
 spec:
-  version: v5.3.0
+  version: v5.4.0
   ...
   pd:
     baseImage: pingcap/pd-enterprise
@@ -56,7 +56,7 @@ spec:
 
 ```yaml
 spec:
-  version: v5.3.0
+  version: v5.4.0
   ...
   pd:
     baseImage: pingcap/pd

en/enable-tls-between-components.md

@@ -1334,7 +1334,7 @@ In this step, you need to perform the following operations:
     spec:
      tlsCluster:
        enabled: true
-     version: v5.3.0
+     version: v5.4.0
      timezone: UTC
      pvReclaimPolicy: Retain
      pd:
@@ -1393,7 +1393,7 @@ In this step, you need to perform the following operations:
        version: 7.5.11
      initializer:
        baseImage: pingcap/tidb-monitor-initializer
-       version: v5.3.0
+       version: v5.4.0
      reloader:
        baseImage: pingcap/tidb-monitor-reloader
        version: v1.0.1

en/enable-tls-for-dm.md

@@ -518,7 +518,7 @@ metadata:
 spec:
   tlsCluster:
     enabled: true
-  version: v5.3.0
+  version: v5.4.0
   pvReclaimPolicy: Retain
   discovery: {}
   master:
@@ -588,7 +588,7 @@ metadata:
   name: ${cluster_name}
   namespace: ${namespace}
 spec:
-  version: v5.3.0
+  version: v5.4.0
   pvReclaimPolicy: Retain
   discovery: {}
   tlsClientSecretNames:

en/enable-tls-for-mysql-client.md

@@ -545,7 +545,7 @@ In this step, you create a TiDB cluster and perform the following operations:
           name: ${cluster_name}
           namespace: ${namespace}
         spec:
-          version: v5.3.0
+          version: v5.4.0
           timezone: UTC
           pvReclaimPolicy: Retain
           pd:

en/get-started.md

@@ -484,10 +484,10 @@ APPROXIMATE_KEYS: 0
 ```sql
 mysql> select tidb_version()\G
 *************************** 1. row ***************************
-  tidb_version(): Release Version: v5.3.0
+  tidb_version(): Release Version: v5.4.0
          Edition: Community
  Git Commit Hash: 4a1b2e9fe5b5afb1068c56de47adb07098d768d6
-      Git Branch: heads/refs/tags/v5.3.0
+      Git Branch: heads/refs/tags/v5.4.0
   UTC Build Time: 2021-11-24 13:32:39
        GoVersion: go1.16.4
     Race Enabled: false