en, zh: bump tidb version to 4.0.7 (#769)

en/access-dashboard.md

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

en/access-tidb.md

@@ -86,7 +86,7 @@ kind: TidbCluster
 metadata:
   name: basic
 spec:
-  version: v4.0.6
+  version: v4.0.7
   pvReclaimPolicy: Retain
   discovery: {}
   pd:

en/advanced-statefulset.md

@@ -79,7 +79,7 @@ kind: TidbCluster
 metadata:
   name: asts
 spec:
-  version: v4.0.6
+  version: v4.0.7
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -128,7 +128,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[1]'
   name: asts
 spec:
-  version: v4.0.6
+  version: v4.0.7
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:
@@ -179,7 +179,7 @@ metadata:
     tikv.tidb.pingcap.com/delete-slots: '[]'
   name: asts
 spec:
-  version: v4.0.6
+  version: v4.0.7
   timezone: UTC
   pvReclaimPolicy: Delete
   pd:

en/configure-a-tidb-cluster.md

@@ -40,11 +40,11 @@ The cluster name can be configured by changing `metadata.name` in the `TiDBCuste
 Usually, components in a cluster are in the same version. It is recommended to configure `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.baseImage` and `spec.version`, if you need to configure different versions for different components, you can configure `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`.
 Here are the formats of the parameters:
 
-- `spec.version`: the format is `imageTag`, such as `v4.0.6`
+- `spec.version`: the format is `imageTag`, such as `v4.0.7`
 
 - `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 `v4.0.6`
+- `spec.<pd/tidb/tikv/pump/tiflash/ticdc>.version`: the format is `imageTag`, such as `v4.0.7`
 
 ### Recommended configuration
 
@@ -184,7 +184,7 @@ metadata:
 spec:
 ....
   tidb:
-    image: pingcap/tidb:v4.0.6
+    image: pingcap/tidb:v4.0.7
     imagePullPolicy: IfNotPresent
     replicas: 1
     service:
@@ -206,7 +206,7 @@ metadata:
 spec:
 ....
   tidb:
-    image: pingcap/tidb:v4.0.6
+    image: pingcap/tidb:v4.0.7
     imagePullPolicy: IfNotPresent
     replicas: 1
     service:
@@ -238,7 +238,7 @@ metadata:
 spec:
 ....
   tikv:
-    image: pingcap/tikv:v4.0.6
+    image: pingcap/tikv:v4.0.7
     config:
       log-level: "info"
       slow-log-threshold: "1s"
@@ -257,7 +257,7 @@ metadata:
 spec:
 ....
   tikv:
-    image: pingcap/tikv:v4.0.6
+    image: pingcap/tikv:v4.0.7
     config: |
       #  [storage]
       #    reserve-space = "2MB"
@@ -286,7 +286,7 @@ metadata:
 spec:
 .....
   pd:
-    image: pingcap/pd:v4.0.6
+    image: pingcap/pd:v4.0.7
     config:
       lease: 3
       enable-prevote: true
@@ -302,7 +302,7 @@ metadata:
 spec:
 .....
   pd:
-    image: pingcap/pd:v4.0.6
+    image: pingcap/pd:v4.0.7
     config: |
       lease = 3
       enable-prevote = true

en/deploy-heterogeneous-tidb-cluster.md

@@ -28,7 +28,7 @@ metadata:
   name: ${heterogeneous_cluster_name}
 spec:
   configUpdateStrategy: RollingUpdate
-  version: v4.0.6
+  version: v4.0.7
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}
@@ -92,7 +92,7 @@ spec:
     version: 6.1.6
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -133,7 +133,7 @@ spec:
   tlsCluster:
     enabled: true
   configUpdateStrategy: RollingUpdate
-  version: v4.0.6
+  version: v4.0.7
   timezone: UTC
   pvReclaimPolicy: Delete
   discovery: {}

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 v4.0.6):
+    To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v4.0.7):
 
     ```shell
-    pingcap/pd:v4.0.6
-    pingcap/tikv:v4.0.6
-    pingcap/tidb:v4.0.6
-    pingcap/tidb-binlog:v4.0.6
-    pingcap/ticdc:v4.0.6
-    pingcap/tiflash:v4.0.6
+    pingcap/pd:v4.0.7
+    pingcap/tikv:v4.0.7
+    pingcap/tidb:v4.0.7
+    pingcap/tidb-binlog:v4.0.7
+    pingcap/ticdc:v4.0.7
+    pingcap/tiflash:v4.0.7
     pingcap/tidb-monitor-reloader:v1.0.1
-    pingcap/tidb-monitor-initializer:v4.0.6
+    pingcap/tidb-monitor-initializer:v4.0.7
     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:v4.0.6
-    docker pull pingcap/tikv:v4.0.6
-    docker pull pingcap/tidb:v4.0.6
-    docker pull pingcap/tidb-binlog:v4.0.6
-    docker pull pingcap/ticdc:v4.0.6
-    docker pull pingcap/tiflash:v4.0.6
+    docker pull pingcap/pd:v4.0.7
+    docker pull pingcap/tikv:v4.0.7
+    docker pull pingcap/tidb:v4.0.7
+    docker pull pingcap/tidb-binlog:v4.0.7
+    docker pull pingcap/ticdc:v4.0.7
+    docker pull pingcap/tiflash:v4.0.7
     docker pull pingcap/tidb-monitor-reloader:v1.0.1
-    docker pull pingcap/tidb-monitor-initializer:v4.0.6
+    docker pull pingcap/tidb-monitor-initializer:v4.0.7
     docker pull grafana/grafana:6.0.1
     docker pull prom/prometheus:v2.18.1
     docker pull busybox:1.26.2
 
-    docker save -o pd-v4.0.6.tar pingcap/pd:v4.0.6
-    docker save -o tikv-v4.0.6.tar pingcap/tikv:v4.0.6
-    docker save -o tidb-v4.0.6.tar pingcap/tidb:v4.0.6
-    docker save -o tidb-binlog-v4.0.6.tar pingcap/tidb-binlog:v4.0.6
-    docker save -o ticdc-v4.0.6.tar pingcap/ticdc:v4.0.6
-    docker save -o tiflash-v4.0.6.tar pingcap/tiflash:v4.0.6
+    docker save -o pd-v4.0.7.tar pingcap/pd:v4.0.7
+    docker save -o tikv-v4.0.7.tar pingcap/tikv:v4.0.7
+    docker save -o tidb-v4.0.7.tar pingcap/tidb:v4.0.7
+    docker save -o tidb-binlog-v4.0.7.tar pingcap/tidb-binlog:v4.0.7
+    docker save -o ticdc-v4.0.7.tar pingcap/ticdc:v4.0.7
+    docker save -o tiflash-v4.0.7.tar pingcap/tiflash:v4.0.7
     docker save -o tidb-monitor-reloader-v1.0.1.tar pingcap/tidb-monitor-reloader:v1.0.1
-    docker save -o tidb-monitor-initializer-v4.0.6.tar pingcap/tidb-monitor-initializer:v4.0.6
+    docker save -o tidb-monitor-initializer-v4.0.7.tar pingcap/tidb-monitor-initializer:v4.0.7
     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-v4.0.6.tar
-    docker load -i tikv-v4.0.6.tar
-    docker load -i tidb-v4.0.6.tar
-    docker load -i tidb-binlog-v4.0.6.tar
-    docker load -i ticdc-v4.0.6.tar
-    docker load -i tiflash-v4.0.6.tar
+    docker load -i pd-v4.0.7.tar
+    docker load -i tikv-v4.0.7.tar
+    docker load -i tidb-v4.0.7.tar
+    docker load -i tidb-binlog-v4.0.7.tar
+    docker load -i ticdc-v4.0.7.tar
+    docker load -i tiflash-v4.0.7.tar
     docker load -i tidb-monitor-reloader-v1.0.1.tar
-    docker load -i tidb-monitor-initializer-v4.0.6.tar
+    docker load -i tidb-monitor-initializer-v4.0.7.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

@@ -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: v4.0.6
+        version: v4.0.7
         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: v4.0.6
+        version: v4.0.7
         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: v4.0.6
+    clusterVersion: v4.0.7
     baseImage:pingcap/tidb-binlog
     storageClassName: local-storage
     storage: 10Gi
@@ -228,7 +228,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust
 
     ```yaml
     ...
-    clusterVersion: v4.0.6
+    clusterVersion: v4.0.7
     baseImage: pingcap/tidb-binlog-enterprise
     ...
     ```

en/deploy-tidb-enterprise-edition.md

@@ -21,7 +21,7 @@ Currently, the difference between the deployment of TiDB Operator Enterprise Edi
 
 ```yaml
 spec:
-  version: v4.0.6
+  version: v4.0.7
   ...
   pd:
     baseImage: pingcap/pd-enterprise
@@ -57,7 +57,7 @@ spec:
 
 ```yaml
 spec:
-  version: v4.0.6
+  version: v4.0.7
   ...
   pd:
     baseImage: pingcap/pd

en/enable-tls-between-components.md

@@ -1109,7 +1109,7 @@ In this step, you need to perform the following operations:
     spec:
      tlsCluster:
        enabled: true
-     version: v4.0.6
+     version: v4.0.7
      timezone: UTC
      pvReclaimPolicy: Retain
      pd:
@@ -1165,7 +1165,7 @@ In this step, you need to perform the following operations:
        version: 6.0.1
      initializer:
        baseImage: pingcap/tidb-monitor-initializer
-       version: v4.0.6
+       version: v4.0.7
      reloader:
        baseImage: pingcap/tidb-monitor-reloader
        version: v1.0.1

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

@@ -503,7 +503,7 @@ In this step, you create a TiDB cluster and perform the following operations:
           name: ${cluster_name}
           amespace: ${namespace}
         spec:
-          version: v4.0.6
+          version: v4.0.7
           timezone: UTC
           pvReclaimPolicy: Retain
           pd:

en/monitor-using-tidbmonitor.md

@@ -49,7 +49,7 @@ spec:
     version: 6.0.1
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -130,7 +130,7 @@ spec:
       type: NodePort
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -178,7 +178,7 @@ spec:
       type: NodePort
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -232,7 +232,7 @@ spec:
         foo: "bar"
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1
@@ -269,7 +269,7 @@ spec:
       type: ClusterIP
   initializer:
     baseImage: pingcap/tidb-monitor-initializer
-    version: v4.0.6
+    version: v4.0.7
   reloader:
     baseImage: pingcap/tidb-monitor-reloader
     version: v1.0.1

en/notes-tidb-operator-v1.1.md

@@ -70,7 +70,7 @@ spec
   ...
   pump:
     baseImage: pingcap/tidb-binlog
-    version: v4.0.6
+    version: v4.0.7
     replicas: 1
     storageClassName: local-storage
     requests:

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 `v4.0.6`.
+    In the command above, `${version}` is the version of the TiDB cluster, such as `v4.0.7`.
 
 2. Unpack the TiDB package for installation:
 

en/restart-a-tidb-cluster.md

@@ -26,7 +26,7 @@ If you find that the memory leak occurs in a Pod during use, you need to restart
     metadata:
       name: basic
     spec:
-      version: v4.0.6
+      version: v4.0.7
       timezone: UTC
       pvReclaimPolicy: Delete
       pd:

en/restore-data-using-tidb-lightning.md

@@ -42,7 +42,7 @@ You can deploy tikv-importer using the Helm chart. See the following example:
 
     ```yaml
     clusterName: demo
-    image: pingcap/tidb-lightning:v4.0.6
+    image: pingcap/tidb-lightning:v4.0.7
     imagePullPolicy: IfNotPresent
     storageClassName: local-storage
     storage: 20Gi