en,zh; Bump tidb components to v5.1.1 (#1355)

pingcap · Aug 18, 2021 · 5b88723 · 5b88723
1 parent 82ae86c
commit 5b88723
Show file tree

Hide file tree

Showing 36 changed files with 135 additions and 135 deletions.
diff --git a/en/access-dashboard.md b/en/access-dashboard.md
@@ -50,7 +50,7 @@ TiDB Dashboard is built in the PD component in TiDB 4.0 and later versions. You
     metadata:
       name: basic
     spec:
-      version: v5.1.0
+      version: v5.1.1
       timezone: UTC
       pvReclaimPolicy: Delete
       pd:

diff --git a/en/advanced-statefulset.md b/en/advanced-statefulset.md
@@ -79,7 +79,7 @@ kind: TidbCluster
 metadata:
   name: asts
 spec:
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -128,7 +128,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[1]'
   name: asts
 spec:
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -179,7 +179,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[]'
   name: asts
 spec:
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:

diff --git a/en/backup-restore-overview.md b/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.1.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.1.1`, 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.1.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.1.1`. 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.1.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.1.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.1.1`. 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.1.1`. 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.

diff --git a/en/configure-a-tidb-cluster.md b/en/configure-a-tidb-cluster.md
@@ -41,11 +41,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.1.0`
+- `spec.version`: the format is `imageTag`, such as `v5.1.1`
 
 - `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.1.0`
+- `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`: the format is `imageTag`, such as `v5.1.1`
 
 ### Recommended configuration
 
@@ -177,7 +177,7 @@ kind: TidbCluster
 metadata:
   name: basic
 spec:
-  version: v5.1.0
+  version: v5.1.1
   pvReclaimPolicy: Retain
   discovery:
     limits:
@@ -293,7 +293,7 @@ metadata:
 spec:
 ....
   tidb:
-    image: pingcap/tidb:v5.1.0
+    image: pingcap/tidb:v5.1.1
     imagePullPolicy: IfNotPresent
     replicas: 1
     service:
@@ -450,7 +450,7 @@ kind: TidbCluster
 metadata:
   name: basic
 spec:
-  version: v5.1.0
+  version: v5.1.1
   pvReclaimPolicy: Retain
   discovery: {}
   pd:

diff --git a/en/deploy-heterogeneous-tidb-cluster.md b/en/deploy-heterogeneous-tidb-cluster.md
@@ -28,7 +28,7 @@ metadata:
   name: ${heterogeneous_cluster_name}
 spec:
   configUpdateStrategy: RollingUpdate
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}
@@ -92,7 +92,7 @@ spec:
     version: 6.1.6
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -133,7 +133,7 @@ spec:
   tlsCluster:
     enabled: true
   configUpdateStrategy: RollingUpdate
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}

diff --git a/en/deploy-on-aws-eks.md b/en/deploy-on-aws-eks.md
@@ -31,7 +31,7 @@ To verify whether AWS CLI is configured correctly, run the `aws configure list`
 
 ## Create a EKS cluster and a node pool
 
-According to AWS [Official Blog](https://aws.amazon.com/blogs/containers/amazon-eks-cluster-multi-zone-auto-scaling-groups/) recommendation and EKS [Best Practice Document](https://aws.github.io/aws-eks-best-practices/reliability/docs/dataplane.html#ensure-capacity-in-each-az-when-using-ebs-volumes), since most of the TiDB cluster components use EBS volumes as storage, it is recommended to create a node pool in each availability zone (at least 3 in total) for each component when creating an EKS.
+According to AWS [Official Blog](https://aws.amazon.com/blogs/containers/amazon-eks-cluster-multi-zone-auto-scaling-groups/) recommendation and EKS [Best Practice Document](https://aws.github.io/aws-eks-best-practices/reliability/docs/dataplane/#ensure-capacity-in-each-az-when-using-ebs-volumes), since most of the TiDB cluster components use EBS volumes as storage, it is recommended to create a node pool in each availability zone (at least 3 in total) for each component when creating an EKS.
 
 Save the following configuration as the `cluster.yaml` file. Replace `${clusterName}` with your desired cluster name. The cluster and node group names should match the regular expression `[a-zA-Z][-a-zA-Z0-9]*`, so avoid names that contain `_`.
 

diff --git a/en/deploy-on-general-kubernetes.md b/en/deploy-on-general-kubernetes.md
@@ -42,17 +42,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.1.0):
+    To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v5.1.1):
 
     ```shell
-    pingcap/pd:v5.1.0
-    pingcap/tikv:v5.1.0
-    pingcap/tidb:v5.1.0
-    pingcap/tidb-binlog:v5.1.0
-    pingcap/ticdc:v5.1.0
-    pingcap/tiflash:v5.1.0
+    pingcap/pd:v5.1.1
+    pingcap/tikv:v5.1.1
+    pingcap/tidb:v5.1.1
+    pingcap/tidb-binlog:v5.1.1
+    pingcap/ticdc:v5.1.1
+    pingcap/tiflash:v5.1.1
     pingcap/tidb-monitor-reloader:v1.0.1
-    pingcap/tidb-monitor-initializer:v5.1.0
+    pingcap/tidb-monitor-initializer:v5.1.1
     grafana/grafana:6.0.1
     prom/prometheus:v2.18.1
     busybox:1.26.2
@@ -63,26 +63,26 @@ This document describes how to deploy a TiDB cluster in general Kubernetes.
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker pull pingcap/pd:v5.1.0
-    docker pull pingcap/tikv:v5.1.0
-    docker pull pingcap/tidb:v5.1.0
-    docker pull pingcap/tidb-binlog:v5.1.0
-    docker pull pingcap/ticdc:v5.1.0
-    docker pull pingcap/tiflash:v5.1.0
+    docker pull pingcap/pd:v5.1.1
+    docker pull pingcap/tikv:v5.1.1
+    docker pull pingcap/tidb:v5.1.1
+    docker pull pingcap/tidb-binlog:v5.1.1
+    docker pull pingcap/ticdc:v5.1.1
+    docker pull pingcap/tiflash:v5.1.1
     docker pull pingcap/tidb-monitor-reloader:v1.0.1
-    docker pull pingcap/tidb-monitor-initializer:v5.1.0
+    docker pull pingcap/tidb-monitor-initializer:v5.1.1
     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.1.0.tar pingcap/pd:v5.1.0
-    docker save -o tikv-v5.1.0.tar pingcap/tikv:v5.1.0
-    docker save -o tidb-v5.1.0.tar pingcap/tidb:v5.1.0
-    docker save -o tidb-binlog-v5.1.0.tar pingcap/tidb-binlog:v5.1.0
-    docker save -o ticdc-v5.1.0.tar pingcap/ticdc:v5.1.0
-    docker save -o tiflash-v5.1.0.tar pingcap/tiflash:v5.1.0
+    docker save -o pd-v5.1.1.tar pingcap/pd:v5.1.1
+    docker save -o tikv-v5.1.1.tar pingcap/tikv:v5.1.1
+    docker save -o tidb-v5.1.1.tar pingcap/tidb:v5.1.1
+    docker save -o tidb-binlog-v5.1.1.tar pingcap/tidb-binlog:v5.1.1
+    docker save -o ticdc-v5.1.1.tar pingcap/ticdc:v5.1.1
+    docker save -o tiflash-v5.1.1.tar pingcap/tiflash:v5.1.1
     docker save -o tidb-monitor-reloader-v1.0.1.tar pingcap/tidb-monitor-reloader:v1.0.1
-    docker save -o tidb-monitor-initializer-v5.1.0.tar pingcap/tidb-monitor-initializer:v5.1.0
+    docker save -o tidb-monitor-initializer-v5.1.1.tar pingcap/tidb-monitor-initializer:v5.1.1
     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
@@ -93,14 +93,14 @@ This document describes how to deploy a TiDB cluster in general Kubernetes.
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker load -i pd-v5.1.0.tar
-    docker load -i tikv-v5.1.0.tar
-    docker load -i tidb-v5.1.0.tar
-    docker load -i tidb-binlog-v5.1.0.tar
-    docker load -i ticdc-v5.1.0.tar
-    docker load -i tiflash-v5.1.0.tar
+    docker load -i pd-v5.1.1.tar
+    docker load -i tikv-v5.1.1.tar
+    docker load -i tidb-v5.1.1.tar
+    docker load -i tidb-binlog-v5.1.1.tar
+    docker load -i ticdc-v5.1.1.tar
+    docker load -i tiflash-v5.1.1.tar
     docker load -i tidb-monitor-reloader-v1.0.1.tar
-    docker load -i tidb-monitor-initializer-v5.1.0.tar
+    docker load -i tidb-monitor-initializer-v5.1.1.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

diff --git a/en/deploy-tidb-binlog.md b/en/deploy-tidb-binlog.md
@@ -28,7 +28,7 @@ TiDB Binlog is disabled in the TiDB cluster by default. To create a TiDB cluster
       ...
       pump:
         baseImage: pingcap/tidb-binlog
-        version: v5.1.0
+        version: v5.1.1
         replicas: 1
         storageClassName: local-storage
         requests:
@@ -47,7 +47,7 @@ TiDB Binlog is disabled in the TiDB cluster by default. To create a TiDB cluster
       ...
       pump:
         baseImage: pingcap/tidb-binlog
-        version: v5.1.0
+        version: v5.1.1
         replicas: 1
         storageClassName: local-storage
         requests:
@@ -198,7 +198,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust
 
     ```yaml
     clusterName: example-tidb
-    clusterVersion: v5.1.0
+    clusterVersion: v5.1.1
     baseImage:pingcap/tidb-binlog
     storageClassName: local-storage
     storage: 10Gi
@@ -231,7 +231,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust
 
     ```yaml
     ...
-    clusterVersion: v5.1.0
+    clusterVersion: v5.1.1
     baseImage: pingcap/tidb-binlog-enterprise
     ...
     ```

diff --git a/en/deploy-tidb-enterprise-edition.md b/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.1.0
+  version: v5.1.1
   ...
   pd:
     baseImage: pingcap/pd-enterprise
@@ -56,7 +56,7 @@ spec:
 
 ```yaml
 spec:
-  version: v5.1.0
+  version: v5.1.1
   ...
   pd:
     baseImage: pingcap/pd

diff --git a/en/enable-tls-between-components.md b/en/enable-tls-between-components.md
@@ -1319,7 +1319,7 @@ In this step, you need to perform the following operations:
     spec:
      tlsCluster:
        enabled: true
-     version: v5.1.0
+     version: v5.1.1
      timezone: UTC
      pvReclaimPolicy: Retain
      pd:
@@ -1375,7 +1375,7 @@ In this step, you need to perform the following operations:
        version: 6.0.1
      initializer:
        baseImage: pingcap/tidb-monitor-initializer
-       version: v5.1.0
+       version: v5.1.1
      reloader:
        baseImage: pingcap/tidb-monitor-reloader
        version: v1.0.1

diff --git a/en/enable-tls-for-mysql-client.md b/en/enable-tls-for-mysql-client.md
@@ -539,7 +539,7 @@ In this step, you create a TiDB cluster and perform the following operations:
           name: ${cluster_name}
           amespace: ${namespace}
         spec:
-          version: v5.1.0
+          version: v5.1.1
           timezone: UTC
           pvReclaimPolicy: Retain
           pd:

diff --git a/en/monitor-a-tidb-cluster.md b/en/monitor-a-tidb-cluster.md
@@ -49,7 +49,7 @@ spec:
       type: NodePort
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -157,7 +157,7 @@ spec:
       type: NodePort
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -211,7 +211,7 @@ spec:
         foo: "bar"
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -248,7 +248,7 @@ spec:
       type: ClusterIP
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -325,7 +325,7 @@ spec:
       type: NodePort
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v5.1.0
+    version: v5.1.1
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1

diff --git a/en/notes-tidb-operator-v1.1.md b/en/notes-tidb-operator-v1.1.md
@@ -70,7 +70,7 @@ spec
   ...
   pump:
     baseImage: pingcap/tidb-binlog
-    version: v5.1.0
+    version: v5.1.1
     replicas: 1
     storageClassName: local-storage
     requests:

diff --git a/en/pd-recover.md b/en/pd-recover.md
@@ -18,7 +18,7 @@ aliases: ['/docs/tidb-in-kubernetes/dev/pd-recover/']
     wget https://download.pingcap.org/tidb-${version}-linux-amd64.tar.gz
     ```
 
-    In the command above, `${version}` is the version of the TiDB cluster, such as `v5.1.0`.
+    In the command above, `${version}` is the version of the TiDB cluster, such as `v5.1.1`.
 
 2. Unpack the TiDB package for installation:
 

diff --git a/en/restart-a-tidb-cluster.md b/en/restart-a-tidb-cluster.md
@@ -32,7 +32,7 @@ kind: TidbCluster
 metadata:
   name: basic
 spec:
-  version: v5.1.0
+  version: v5.1.1
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:

diff --git a/en/restore-data-using-tidb-lightning.md b/en/restore-data-using-tidb-lightning.md
@@ -52,7 +52,7 @@ You can deploy tikv-importer using the Helm chart. See the following example:
 
     ```yaml
     clusterName: demo
-    image: pingcap/tidb-lightning:v5.1.0
+    image: pingcap/tidb-lightning:v5.1.1
     imagePullPolicy: IfNotPresent
     storageClassName: local-storage
     storage: 20Gi

diff --git a/en/upgrade-a-tidb-cluster.md b/en/upgrade-a-tidb-cluster.md
@@ -29,7 +29,7 @@ If the TiDB cluster is deployed directly using TidbCluster CR, or deployed using
 
     The `version` field has following formats:
 
-    - `spec.version`: the format is `imageTag`, such as `v5.1.0`
+    - `spec.version`: the format is `imageTag`, such as `v5.1.1`
 
     - `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`: the format is `imageTag`, such as `v3.1.0`