From ab0a83e236944260aecece52facb885a66a174a4 Mon Sep 17 00:00:00 2001 From: ti-srebot <66930949+ti-srebot@users.noreply.github.com> Date: Mon, 21 Dec 2020 17:39:08 +0800 Subject: [PATCH] en, zh: bump tidb version to v4.0.9 (#928) (#937) Signed-off-by: ti-srebot --- en/access-dashboard.md | 2 +- en/access-tidb.md | 2 +- en/advanced-statefulset.md | 6 +-- en/configure-a-tidb-cluster.md | 16 +++---- en/deploy-heterogeneous-tidb-cluster.md | 6 +-- en/deploy-on-general-kubernetes.md | 58 ++++++++++++------------- en/deploy-tidb-binlog.md | 8 ++-- en/deploy-tidb-enterprise-edition.md | 4 +- en/enable-tls-between-components.md | 4 +- en/enable-tls-for-mysql-client.md | 2 +- en/monitor-using-tidbmonitor.md | 10 ++--- en/notes-tidb-operator-v1.1.md | 2 +- en/pd-recover.md | 2 +- en/restart-a-tidb-cluster.md | 2 +- en/restore-data-using-tidb-lightning.md | 2 +- en/upgrade-a-tidb-cluster.md | 4 +- zh/access-dashboard.md | 2 +- zh/access-tidb.md | 2 +- zh/advanced-statefulset.md | 6 +-- zh/configure-a-tidb-cluster.md | 16 +++---- zh/deploy-heterogeneous-tidb-cluster.md | 6 +-- zh/deploy-on-gcp-gke.md | 2 +- zh/deploy-on-general-kubernetes.md | 58 ++++++++++++------------- zh/deploy-tidb-binlog.md | 8 ++-- zh/deploy-tidb-enterprise-edition.md | 4 +- zh/enable-tls-between-components.md | 4 +- zh/enable-tls-for-mysql-client.md | 2 +- zh/monitor-using-tidbmonitor.md | 10 ++--- zh/notes-tidb-operator-v1.1.md | 2 +- zh/pd-recover.md | 2 +- zh/restart-a-tidb-cluster.md | 2 +- zh/restore-data-using-tidb-lightning.md | 2 +- zh/upgrade-a-tidb-cluster.md | 4 +- 33 files changed, 131 insertions(+), 131 deletions(-) diff --git a/en/access-dashboard.md b/en/access-dashboard.md index 98c99e8722..76c0ba4f03 100644 --- a/en/access-dashboard.md +++ b/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.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/access-tidb.md b/en/access-tidb.md index b1b8bc6987..7e2395f60a 100644 --- a/en/access-tidb.md +++ b/en/access-tidb.md @@ -86,7 +86,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.8 + version: v4.0.9 pvReclaimPolicy: Retain discovery: {} pd: diff --git a/en/advanced-statefulset.md b/en/advanced-statefulset.md index cad2cc81e1..7295c58695 100644 --- a/en/advanced-statefulset.md +++ b/en/advanced-statefulset.md @@ -79,7 +79,7 @@ kind: TidbCluster metadata: name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: @@ -128,7 +128,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[1]' name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: @@ -179,7 +179,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[]' name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/configure-a-tidb-cluster.md b/en/configure-a-tidb-cluster.md index 7149b9cbbd..117ba87224 100644 --- a/en/configure-a-tidb-cluster.md +++ b/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..baseImage` and `spec.version`, if you need to configure different versions for different components, you can configure `spec..version`. Here are the formats of the parameters: -- `spec.version`: the format is `imageTag`, such as `v4.0.8` +- `spec.version`: the format is `imageTag`, such as `v4.0.9` - `spec..baseImage`: the format is `imageName`, such as `pingcap/tidb` -- `spec..version`: the format is `imageTag`, such as `v4.0.8` +- `spec..version`: the format is `imageTag`, such as `v4.0.9` ### Recommended configuration @@ -262,7 +262,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.8 + image: pingcap/tidb:v4.0.9 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -284,7 +284,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.8 + image: pingcap/tidb:v4.0.9 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -316,7 +316,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.8 + image: pingcap/tikv:v4.0.9 config: log-level: "info" slow-log-threshold: "1s" @@ -335,7 +335,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.8 + image: pingcap/tikv:v4.0.9 config: | # [storage] # reserve-space = "2MB" @@ -364,7 +364,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.8 + image: pingcap/pd:v4.0.9 config: lease: 3 enable-prevote: true @@ -380,7 +380,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.8 + image: pingcap/pd:v4.0.9 config: | lease = 3 enable-prevote = true diff --git a/en/deploy-heterogeneous-tidb-cluster.md b/en/deploy-heterogeneous-tidb-cluster.md index b27b2bb6d7..8b0f03f3d1 100644 --- 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: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete discovery: {} @@ -92,7 +92,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -133,7 +133,7 @@ spec: tlsCluster: enabled: true configUpdateStrategy: RollingUpdate - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete discovery: {} diff --git a/en/deploy-on-general-kubernetes.md b/en/deploy-on-general-kubernetes.md index 705629f432..cc50855e2a 100644 --- 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 v4.0.8): + To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v4.0.9): ```shell - pingcap/pd:v4.0.8 - pingcap/tikv:v4.0.8 - pingcap/tidb:v4.0.8 - pingcap/tidb-binlog:v4.0.8 - pingcap/ticdc:v4.0.8 - pingcap/tiflash:v4.0.8 + pingcap/pd:v4.0.9 + pingcap/tikv:v4.0.9 + pingcap/tidb:v4.0.9 + pingcap/tidb-binlog:v4.0.9 + pingcap/ticdc:v4.0.9 + pingcap/tiflash:v4.0.9 pingcap/tidb-monitor-reloader:v1.0.1 - pingcap/tidb-monitor-initializer:v4.0.8 + pingcap/tidb-monitor-initializer:v4.0.9 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.8 - docker pull pingcap/tikv:v4.0.8 - docker pull pingcap/tidb:v4.0.8 - docker pull pingcap/tidb-binlog:v4.0.8 - docker pull pingcap/ticdc:v4.0.8 - docker pull pingcap/tiflash:v4.0.8 + docker pull pingcap/pd:v4.0.9 + docker pull pingcap/tikv:v4.0.9 + docker pull pingcap/tidb:v4.0.9 + docker pull pingcap/tidb-binlog:v4.0.9 + docker pull pingcap/ticdc:v4.0.9 + docker pull pingcap/tiflash:v4.0.9 docker pull pingcap/tidb-monitor-reloader:v1.0.1 - docker pull pingcap/tidb-monitor-initializer:v4.0.8 + docker pull pingcap/tidb-monitor-initializer:v4.0.9 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.8.tar pingcap/pd:v4.0.8 - docker save -o tikv-v4.0.8.tar pingcap/tikv:v4.0.8 - docker save -o tidb-v4.0.8.tar pingcap/tidb:v4.0.8 - docker save -o tidb-binlog-v4.0.8.tar pingcap/tidb-binlog:v4.0.8 - docker save -o ticdc-v4.0.8.tar pingcap/ticdc:v4.0.8 - docker save -o tiflash-v4.0.8.tar pingcap/tiflash:v4.0.8 + docker save -o pd-v4.0.9.tar pingcap/pd:v4.0.9 + docker save -o tikv-v4.0.9.tar pingcap/tikv:v4.0.9 + docker save -o tidb-v4.0.9.tar pingcap/tidb:v4.0.9 + docker save -o tidb-binlog-v4.0.9.tar pingcap/tidb-binlog:v4.0.9 + docker save -o ticdc-v4.0.9.tar pingcap/ticdc:v4.0.9 + docker save -o tiflash-v4.0.9.tar pingcap/tiflash:v4.0.9 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.8.tar pingcap/tidb-monitor-initializer:v4.0.8 + docker save -o tidb-monitor-initializer-v4.0.9.tar pingcap/tidb-monitor-initializer:v4.0.9 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.8.tar - docker load -i tikv-v4.0.8.tar - docker load -i tidb-v4.0.8.tar - docker load -i tidb-binlog-v4.0.8.tar - docker load -i ticdc-v4.0.8.tar - docker load -i tiflash-v4.0.8.tar + docker load -i pd-v4.0.9.tar + docker load -i tikv-v4.0.9.tar + docker load -i tidb-v4.0.9.tar + docker load -i tidb-binlog-v4.0.9.tar + docker load -i ticdc-v4.0.9.tar + docker load -i tiflash-v4.0.9.tar docker load -i tidb-monitor-reloader-v1.0.1.tar - docker load -i tidb-monitor-initializer-v4.0.8.tar + docker load -i tidb-monitor-initializer-v4.0.9.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 index 94b7d82a44..31b2ef947f 100644 --- 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: v4.0.8 + version: v4.0.9 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.8 + version: v4.0.9 replicas: 1 storageClassName: local-storage requests: @@ -208,7 +208,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust ```yaml clusterName: example-tidb - clusterVersion: v4.0.8 + clusterVersion: v4.0.9 baseImage:pingcap/tidb-binlog storageClassName: local-storage storage: 10Gi @@ -238,7 +238,7 @@ To deploy multiple drainers using the `tidb-drainer` Helm chart for a TiDB clust ```yaml ... - clusterVersion: v4.0.8 + clusterVersion: v4.0.9 baseImage: pingcap/tidb-binlog-enterprise ... ``` diff --git a/en/deploy-tidb-enterprise-edition.md b/en/deploy-tidb-enterprise-edition.md index 34965bff36..5ee5c189de 100644 --- 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: v4.0.8 + version: v4.0.9 ... pd: baseImage: pingcap/pd-enterprise @@ -56,7 +56,7 @@ spec: ```yaml spec: - version: v4.0.8 + version: v4.0.9 ... pd: baseImage: pingcap/pd diff --git a/en/enable-tls-between-components.md b/en/enable-tls-between-components.md index aa737fd921..8a975966a4 100644 --- a/en/enable-tls-between-components.md +++ b/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.8 + version: v4.0.9 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.8 + version: v4.0.9 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 index fad8499766..008cf7841b 100644 --- a/en/enable-tls-for-mysql-client.md +++ b/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.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Retain pd: diff --git a/en/monitor-using-tidbmonitor.md b/en/monitor-using-tidbmonitor.md index 54b96739be..cdb90fc9ce 100644 --- a/en/monitor-using-tidbmonitor.md +++ b/en/monitor-using-tidbmonitor.md @@ -49,7 +49,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 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.8 + version: v4.0.9 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.8 + version: v4.0.9 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.8 + version: v4.0.9 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.8 + version: v4.0.9 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 index c05ad2e6bc..971656cba6 100644 --- 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: v4.0.8 + version: v4.0.9 replicas: 1 storageClassName: local-storage requests: diff --git a/en/pd-recover.md b/en/pd-recover.md index 1bbcda0a1e..0b54548bd3 100644 --- a/en/pd-recover.md +++ b/en/pd-recover.md @@ -18,7 +18,7 @@ aliases: ['/docs/tidb-in-kubernetes/stable/pd-recover/','/docs/tidb-in-kubernete 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.8`. + In the command above, `${version}` is the version of the TiDB cluster, such as `v4.0.9`. 2. Unpack the TiDB package for installation: diff --git a/en/restart-a-tidb-cluster.md b/en/restart-a-tidb-cluster.md index c017d0a7ff..8d8a78ef97 100644 --- 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: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/restore-data-using-tidb-lightning.md b/en/restore-data-using-tidb-lightning.md index 762482da6b..d4b1511977 100644 --- a/en/restore-data-using-tidb-lightning.md +++ b/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.8 + image: pingcap/tidb-lightning:v4.0.9 imagePullPolicy: IfNotPresent storageClassName: local-storage storage: 20Gi diff --git a/en/upgrade-a-tidb-cluster.md b/en/upgrade-a-tidb-cluster.md index d03c378f1e..08d932d299 100644 --- 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 `v4.0.8` + - `spec.version`: the format is `imageTag`, such as `v4.0.9` - `spec..version`: the format is `imageTag`, such as `v3.1.0` @@ -87,7 +87,7 @@ If you continue to manage your cluster using Helm, refer to the following steps > > If you want to upgrade to Enterprise Edition, set the value of `.image` to the enterprise image. > - > For example, change `pd.image` from `pingcap/pd:v4.0.8` to `pingcap/pd-enterprise:v4.0.8`. + > For example, change `pd.image` from `pingcap/pd:v4.0.9` to `pingcap/pd-enterprise:v4.0.9`. 2. Run the `helm upgrade` command: diff --git a/zh/access-dashboard.md b/zh/access-dashboard.md index 36b7fef487..53ff4f3d75 100644 --- a/zh/access-dashboard.md +++ b/zh/access-dashboard.md @@ -36,7 +36,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/access-tidb.md b/zh/access-tidb.md index 8ba6bb5704..bef2b71daf 100644 --- a/zh/access-tidb.md +++ b/zh/access-tidb.md @@ -85,7 +85,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.8 + version: v4.0.9 pvReclaimPolicy: Retain discovery: {} pd: diff --git a/zh/advanced-statefulset.md b/zh/advanced-statefulset.md index 64a9292246..15c7e8daf9 100644 --- a/zh/advanced-statefulset.md +++ b/zh/advanced-statefulset.md @@ -77,7 +77,7 @@ kind: TidbCluster metadata: name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: @@ -126,7 +126,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[1]' name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: @@ -177,7 +177,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[]' name: asts spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/configure-a-tidb-cluster.md b/zh/configure-a-tidb-cluster.md index 1fc1093f4b..cc49aaa164 100644 --- a/zh/configure-a-tidb-cluster.md +++ b/zh/configure-a-tidb-cluster.md @@ -40,9 +40,9 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/configure-a-tidb-cluster/','/docs- 相关参数的格式如下： -- `spec.version`，格式为 `imageTag`，例如 `v4.0.8` +- `spec.version`，格式为 `imageTag`，例如 `v4.0.9` - `spec..baseImage`，格式为 `imageName`，例如 `pingcap/tidb` -- `spec..version`，格式为 `imageTag`，例如 `v4.0.8` +- `spec..version`，格式为 `imageTag`，例如 `v4.0.9` ### 推荐配置 @@ -251,7 +251,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.8 + image: pingcap/tidb:v4.0.9 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -273,7 +273,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.8 + image: pingcap/tidb:v4.0.9 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -303,7 +303,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.8 + image: pingcap/tikv:v4.0.9 config: {} replicas: 1 requests: @@ -320,7 +320,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.8 + image: pingcap/tikv:v4.0.9 config: | # [storage] # reserve-space = "2MB" @@ -347,7 +347,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.8 + image: pingcap/pd:v4.0.9 config: lease: 3 enable-prevote: true @@ -363,7 +363,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.8 + image: pingcap/pd:v4.0.9 config: | lease = 3 enable-prevote = true diff --git a/zh/deploy-heterogeneous-tidb-cluster.md b/zh/deploy-heterogeneous-tidb-cluster.md index 9c083a3311..6e71672160 100644 --- a/zh/deploy-heterogeneous-tidb-cluster.md +++ b/zh/deploy-heterogeneous-tidb-cluster.md @@ -30,7 +30,7 @@ metadata: name: ${heterogeneous_cluster_name} spec: configUpdateStrategy: RollingUpdate - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete discovery: {} @@ -94,7 +94,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -133,7 +133,7 @@ spec: tlsCluster: enabled: true configUpdateStrategy: RollingUpdate - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete discovery: {} diff --git a/zh/deploy-on-gcp-gke.md b/zh/deploy-on-gcp-gke.md index adfaa2ec81..11c3d56d55 100644 --- a/zh/deploy-on-gcp-gke.md +++ b/zh/deploy-on-gcp-gke.md @@ -180,7 +180,7 @@ gcloud compute instances create bastion \ $ mysql -h 10.128.15.243 -P 4000 -u root Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 7823 - Server version: 5.7.25-TiDB-v4.0.8 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible + Server version: 5.7.25-TiDB-v4.0.9 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. diff --git a/zh/deploy-on-general-kubernetes.md b/zh/deploy-on-general-kubernetes.md index 94d5005ede..feac4b6add 100644 --- a/zh/deploy-on-general-kubernetes.md +++ b/zh/deploy-on-general-kubernetes.md @@ -43,17 +43,17 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/','/d 如果服务器没有外网，需要在有外网的机器上将 TiDB 集群用到的 Docker 镜像下载下来并上传到服务器上，然后使用 `docker load` 将 Docker 镜像安装到服务器上。 - 部署一套 TiDB 集群会用到下面这些 Docker 镜像（假设 TiDB 集群的版本是 v4.0.8）： + 部署一套 TiDB 集群会用到下面这些 Docker 镜像（假设 TiDB 集群的版本是 v4.0.9）： ```shell - pingcap/pd:v4.0.8 - pingcap/tikv:v4.0.8 - pingcap/tidb:v4.0.8 - pingcap/tidb-binlog:v4.0.8 - pingcap/ticdc:v4.0.8 - pingcap/tiflash:v4.0.8 + pingcap/pd:v4.0.9 + pingcap/tikv:v4.0.9 + pingcap/tidb:v4.0.9 + pingcap/tidb-binlog:v4.0.9 + pingcap/ticdc:v4.0.9 + pingcap/tiflash:v4.0.9 pingcap/tidb-monitor-reloader:v1.0.1 - pingcap/tidb-monitor-initializer:v4.0.8 + pingcap/tidb-monitor-initializer:v4.0.9 grafana/grafana:6.0.1 prom/prometheus:v2.18.1 busybox:1.26.2 @@ -64,26 +64,26 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/','/d {{< copyable "shell-regular" >}} ```shell - docker pull pingcap/pd:v4.0.8 - docker pull pingcap/tikv:v4.0.8 - docker pull pingcap/tidb:v4.0.8 - docker pull pingcap/tidb-binlog:v4.0.8 - docker pull pingcap/ticdc:v4.0.8 - docker pull pingcap/tiflash:v4.0.8 + docker pull pingcap/pd:v4.0.9 + docker pull pingcap/tikv:v4.0.9 + docker pull pingcap/tidb:v4.0.9 + docker pull pingcap/tidb-binlog:v4.0.9 + docker pull pingcap/ticdc:v4.0.9 + docker pull pingcap/tiflash:v4.0.9 docker pull pingcap/tidb-monitor-reloader:v1.0.1 - docker pull pingcap/tidb-monitor-initializer:v4.0.8 + docker pull pingcap/tidb-monitor-initializer:v4.0.9 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.8.tar pingcap/pd:v4.0.8 - docker save -o tikv-v4.0.8.tar pingcap/tikv:v4.0.8 - docker save -o tidb-v4.0.8.tar pingcap/tidb:v4.0.8 - docker save -o tidb-binlog-v4.0.8.tar pingcap/tidb-binlog:v4.0.8 - docker save -o ticdc-v4.0.8.tar pingcap/ticdc:v4.0.8 - docker save -o tiflash-v4.0.8.tar pingcap/tiflash:v4.0.8 + docker save -o pd-v4.0.9.tar pingcap/pd:v4.0.9 + docker save -o tikv-v4.0.9.tar pingcap/tikv:v4.0.9 + docker save -o tidb-v4.0.9.tar pingcap/tidb:v4.0.9 + docker save -o tidb-binlog-v4.0.9.tar pingcap/tidb-binlog:v4.0.9 + docker save -o ticdc-v4.0.9.tar pingcap/ticdc:v4.0.9 + docker save -o tiflash-v4.0.9.tar pingcap/tiflash:v4.0.9 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.8.tar pingcap/tidb-monitor-initializer:v4.0.8 + docker save -o tidb-monitor-initializer-v4.0.9.tar pingcap/tidb-monitor-initializer:v4.0.9 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 @@ -94,14 +94,14 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/','/d {{< copyable "shell-regular" >}} ```shell - docker load -i pd-v4.0.8.tar - docker load -i tikv-v4.0.8.tar - docker load -i tidb-v4.0.8.tar - docker load -i tidb-binlog-v4.0.8.tar - docker load -i ticdc-v4.0.8.tar - docker load -i tiflash-v4.0.8.tar + docker load -i pd-v4.0.9.tar + docker load -i tikv-v4.0.9.tar + docker load -i tidb-v4.0.9.tar + docker load -i tidb-binlog-v4.0.9.tar + docker load -i ticdc-v4.0.9.tar + docker load -i tiflash-v4.0.9.tar docker load -i tidb-monitor-reloader-v1.0.1.tar - docker load -i tidb-monitor-initializer-v4.0.8.tar + docker load -i tidb-monitor-initializer-v4.0.9.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/zh/deploy-tidb-binlog.md b/zh/deploy-tidb-binlog.md index 217820add0..c5433f1287 100644 --- a/zh/deploy-tidb-binlog.md +++ b/zh/deploy-tidb-binlog.md @@ -26,7 +26,7 @@ spec ... pump: baseImage: pingcap/tidb-binlog - version: v4.0.8 + version: v4.0.9 replicas: 1 storageClassName: local-storage requests: @@ -45,7 +45,7 @@ spec ... pump: baseImage: pingcap/tidb-binlog - version: v4.0.8 + version: v4.0.9 replicas: 1 storageClassName: local-storage requests: @@ -202,7 +202,7 @@ spec: ```yaml clusterName: example-tidb - clusterVersion: v4.0.8 + clusterVersion: v4.0.9 baseImage: pingcap/tidb-binlog storageClassName: local-storage storage: 10Gi @@ -232,7 +232,7 @@ spec: ```yaml ... - clusterVersion: v4.0.8 + clusterVersion: v4.0.9 baseImage: pingcap/tidb-binlog-enterprise ... ``` diff --git a/zh/deploy-tidb-enterprise-edition.md b/zh/deploy-tidb-enterprise-edition.md index d6a33c6876..becfe26a1f 100644 --- a/zh/deploy-tidb-enterprise-edition.md +++ b/zh/deploy-tidb-enterprise-edition.md @@ -21,7 +21,7 @@ summary: 了解如何在 Kubernetes 上部署 TiDB 企业版。 ```yaml spec: - version: v4.0.8 + version: v4.0.9 ... pd: baseImage: pingcap/pd-enterprise @@ -52,7 +52,7 @@ TiDB Operator 会自动通过滚动升级的方式将集群镜像更新为企业 ```yaml spec: - version: v4.0.8 + version: v4.0.9 ... pd: baseImage: pingcap/pd diff --git a/zh/enable-tls-between-components.md b/zh/enable-tls-between-components.md index d40c6d496f..67fab69efa 100644 --- a/zh/enable-tls-between-components.md +++ b/zh/enable-tls-between-components.md @@ -1278,7 +1278,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/enable-tls-between-components/','/ spec: tlsCluster: enabled: true - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Retain pd: @@ -1334,7 +1334,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/enable-tls-between-components/','/ version: 6.0.1 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 diff --git a/zh/enable-tls-for-mysql-client.md b/zh/enable-tls-for-mysql-client.md index dec35ebfed..8bf200af9b 100644 --- a/zh/enable-tls-for-mysql-client.md +++ b/zh/enable-tls-for-mysql-client.md @@ -522,7 +522,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/enable-tls-for-mysql-client/','/do name: ${cluster_name} namespace: ${namespace} spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Retain pd: diff --git a/zh/monitor-using-tidbmonitor.md b/zh/monitor-using-tidbmonitor.md index 166519ab81..6acc9c5b10 100644 --- a/zh/monitor-using-tidbmonitor.md +++ b/zh/monitor-using-tidbmonitor.md @@ -47,7 +47,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -120,7 +120,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -163,7 +163,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -213,7 +213,7 @@ spec: foo: "bar" initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -250,7 +250,7 @@ spec: type: ClusterIP initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.8 + version: v4.0.9 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 diff --git a/zh/notes-tidb-operator-v1.1.md b/zh/notes-tidb-operator-v1.1.md index e7e67c813a..c281131a7c 100644 --- a/zh/notes-tidb-operator-v1.1.md +++ b/zh/notes-tidb-operator-v1.1.md @@ -65,7 +65,7 @@ spec ... pump: baseImage: pingcap/tidb-binlog - version: v4.0.8 + version: v4.0.9 replicas: 1 storageClassName: local-storage requests: diff --git a/zh/pd-recover.md b/zh/pd-recover.md index 0376c9565e..d02f0b80f3 100644 --- a/zh/pd-recover.md +++ b/zh/pd-recover.md @@ -18,7 +18,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/pd-recover/','/docs-cn/tidb-in-kub wget https://download.pingcap.org/tidb-${version}-linux-amd64.tar.gz ``` - `${version}` 是 TiDB 集群版本，例如，`v4.0.8`。 + `${version}` 是 TiDB 集群版本，例如，`v4.0.9`。 2. 解压安装包： diff --git a/zh/restart-a-tidb-cluster.md b/zh/restart-a-tidb-cluster.md index ebb236e992..d7a70d1672 100644 --- a/zh/restart-a-tidb-cluster.md +++ b/zh/restart-a-tidb-cluster.md @@ -22,7 +22,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.8 + version: v4.0.9 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/restore-data-using-tidb-lightning.md b/zh/restore-data-using-tidb-lightning.md index d3c89bec24..ae1e56d39f 100644 --- a/zh/restore-data-using-tidb-lightning.md +++ b/zh/restore-data-using-tidb-lightning.md @@ -42,7 +42,7 @@ TiDB Lightning 包含两个组件：tidb-lightning 和 tikv-importer。在 Kuber ```yaml clusterName: demo - image: pingcap/tidb-lightning:v4.0.8 + image: pingcap/tidb-lightning:v4.0.9 imagePullPolicy: IfNotPresent storageClassName: local-storage storage: 20Gi diff --git a/zh/upgrade-a-tidb-cluster.md b/zh/upgrade-a-tidb-cluster.md index fda50b8eb1..d81bf8f8b2 100644 --- a/zh/upgrade-a-tidb-cluster.md +++ b/zh/upgrade-a-tidb-cluster.md @@ -26,7 +26,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/stable/upgrade-a-tidb-cluster/','/docs-cn `version` 字段格式如下： - - `spec.version`，格式为 `imageTag`，例如 `v4.0.8` + - `spec.version`，格式为 `imageTag`，例如 `v4.0.9` - `spec..version`，格式为 `imageTag`，例如 `v3.1.0` {{< copyable "shell-regular" >}} @@ -105,7 +105,7 @@ kubectl annotate --overwrite tc ${cluster_name} -n ${namespace} tidb.pingcap.com > > 如果需要升级到企业版，需要把 `.image` 的值改为企业版镜像。 > -> 例如将 `pd.image` 从 `pingcap/pd:v4.0.8` 修改为 `pingcap/pd-enterprise:v4.0.8`。 +> 例如将 `pd.image` 从 `pingcap/pd:v4.0.9` 修改为 `pingcap/pd-enterprise:v4.0.9`。 ### 强制升级 TiDB 集群