diff --git a/en/access-dashboard.md b/en/access-dashboard.md index d4508fafaa..e65e08c423 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.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/advanced-statefulset.md b/en/advanced-statefulset.md index 8f3588b5ed..ddb9456f87 100644 --- a/en/advanced-statefulset.md +++ b/en/advanced-statefulset.md @@ -79,7 +79,7 @@ kind: TidbCluster metadata: name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: @@ -128,7 +128,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[1]' name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: @@ -179,7 +179,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[]' name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/configure-a-tidb-cluster.md b/en/configure-a-tidb-cluster.md index b701b1822b..608c3a25c2 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.9` +- `spec.version`: the format is `imageTag`, such as `v4.0.10` - `spec..baseImage`: the format is `imageName`, such as `pingcap/tidb` -- `spec..version`: the format is `imageTag`, such as `v4.0.9` +- `spec..version`: the format is `imageTag`, such as `v4.0.10` ### Recommended configuration @@ -272,7 +272,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.9 + image: pingcap/tidb:v4.0.10 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -294,7 +294,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.9 + image: pingcap/tidb:v4.0.10 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -326,7 +326,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.9 + image: pingcap/tikv:v4.0.10 config: log-level: "info" slow-log-threshold: "1s" @@ -345,7 +345,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.9 + image: pingcap/tikv:v4.0.10 config: | # [storage] # reserve-space = "2MB" @@ -374,7 +374,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.9 + image: pingcap/pd:v4.0.10 config: lease: 3 enable-prevote: true @@ -390,7 +390,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.9 + image: pingcap/pd:v4.0.10 config: | lease = 3 enable-prevote = true @@ -490,7 +490,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.9 + version: v4.0.10 pvReclaimPolicy: Retain discovery: {} pd: diff --git a/en/deploy-heterogeneous-tidb-cluster.md b/en/deploy-heterogeneous-tidb-cluster.md index 8b0f03f3d1..fc63394b4e 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.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete discovery: {} @@ -92,7 +92,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -133,7 +133,7 @@ spec: tlsCluster: enabled: true configUpdateStrategy: RollingUpdate - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete discovery: {} diff --git a/en/deploy-on-general-kubernetes.md b/en/deploy-on-general-kubernetes.md index 6c86ab50ad..b0d72c8c04 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.9): + To deploy a TiDB cluster, you need the following Docker images (assuming the version of the TiDB cluster is v4.0.10): ```shell - 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/pd:v4.0.10 + pingcap/tikv:v4.0.10 + pingcap/tidb:v4.0.10 + pingcap/tidb-binlog:v4.0.10 + pingcap/ticdc:v4.0.10 + pingcap/tiflash:v4.0.10 pingcap/tidb-monitor-reloader:v1.0.1 - pingcap/tidb-monitor-initializer:v4.0.9 + pingcap/tidb-monitor-initializer:v4.0.10 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.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/pd:v4.0.10 + docker pull pingcap/tikv:v4.0.10 + docker pull pingcap/tidb:v4.0.10 + docker pull pingcap/tidb-binlog:v4.0.10 + docker pull pingcap/ticdc:v4.0.10 + docker pull pingcap/tiflash:v4.0.10 docker pull pingcap/tidb-monitor-reloader:v1.0.1 - docker pull pingcap/tidb-monitor-initializer:v4.0.9 + docker pull pingcap/tidb-monitor-initializer:v4.0.10 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.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 pd-v4.0.10.tar pingcap/pd:v4.0.10 + docker save -o tikv-v4.0.10.tar pingcap/tikv:v4.0.10 + docker save -o tidb-v4.0.10.tar pingcap/tidb:v4.0.10 + docker save -o tidb-binlog-v4.0.10.tar pingcap/tidb-binlog:v4.0.10 + docker save -o ticdc-v4.0.10.tar pingcap/ticdc:v4.0.10 + docker save -o tiflash-v4.0.10.tar pingcap/tiflash:v4.0.10 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.9.tar pingcap/tidb-monitor-initializer:v4.0.9 + docker save -o tidb-monitor-initializer-v4.0.10.tar pingcap/tidb-monitor-initializer:v4.0.10 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.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 pd-v4.0.10.tar + docker load -i tikv-v4.0.10.tar + docker load -i tidb-v4.0.10.tar + docker load -i tidb-binlog-v4.0.10.tar + docker load -i ticdc-v4.0.10.tar + docker load -i tiflash-v4.0.10.tar docker load -i tidb-monitor-reloader-v1.0.1.tar - docker load -i tidb-monitor-initializer-v4.0.9.tar + docker load -i tidb-monitor-initializer-v4.0.10.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 4ef7dec62e..98f6970192 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.9 + version: v4.0.10 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.9 + version: v4.0.10 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.9 + clusterVersion: v4.0.10 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.9 + clusterVersion: v4.0.10 baseImage: pingcap/tidb-binlog-enterprise ... ``` diff --git a/en/deploy-tidb-enterprise-edition.md b/en/deploy-tidb-enterprise-edition.md index 5ee5c189de..bb833eaa12 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.9 + version: v4.0.10 ... pd: baseImage: pingcap/pd-enterprise @@ -56,7 +56,7 @@ spec: ```yaml spec: - version: v4.0.9 + version: v4.0.10 ... pd: baseImage: pingcap/pd diff --git a/en/enable-tls-between-components.md b/en/enable-tls-between-components.md index ebfd29445a..25b1dadb83 100644 --- a/en/enable-tls-between-components.md +++ b/en/enable-tls-between-components.md @@ -1313,7 +1313,7 @@ In this step, you need to perform the following operations: spec: tlsCluster: enabled: true - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Retain pd: @@ -1369,7 +1369,7 @@ In this step, you need to perform the following operations: version: 6.0.1 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 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 d21aa48546..4f15bf9f17 100644 --- a/en/enable-tls-for-mysql-client.md +++ b/en/enable-tls-for-mysql-client.md @@ -535,7 +535,7 @@ In this step, you create a TiDB cluster and perform the following operations: name: ${cluster_name} amespace: ${namespace} spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Retain pd: diff --git a/en/monitor-a-tidb-cluster.md b/en/monitor-a-tidb-cluster.md index 8dc51da88d..272d236955 100644 --- a/en/monitor-a-tidb-cluster.md +++ b/en/monitor-a-tidb-cluster.md @@ -50,7 +50,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -158,7 +158,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -212,7 +212,7 @@ spec: foo: "bar" initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -249,7 +249,7 @@ spec: type: ClusterIP initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 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 2883ebd278..9dbf54174f 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.9 + version: v4.0.10 replicas: 1 storageClassName: local-storage requests: diff --git a/en/pd-recover.md b/en/pd-recover.md index c9fb4205d0..fa255a3427 100644 --- 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 `v4.0.9`. + In the command above, `${version}` is the version of the TiDB cluster, such as `v4.0.10`. 2. Unpack the TiDB package for installation: diff --git a/en/restart-a-tidb-cluster.md b/en/restart-a-tidb-cluster.md index e8578db336..2b7de275ea 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.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/en/restore-data-using-tidb-lightning.md b/en/restore-data-using-tidb-lightning.md index 04883d2d9f..60f2b3581a 100644 --- 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:v4.0.9 + image: pingcap/tidb-lightning:v4.0.10 imagePullPolicy: IfNotPresent storageClassName: local-storage storage: 20Gi diff --git a/en/upgrade-a-tidb-cluster.md b/en/upgrade-a-tidb-cluster.md index 4dd5002d13..23f5b12e50 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.9` + - `spec.version`: the format is `imageTag`, such as `v4.0.10` - `spec..version`: the format is `imageTag`, such as `v3.1.0` @@ -112,7 +112,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.9` to `pingcap/pd-enterprise:v4.0.9`. + > For example, change `pd.image` from `pingcap/pd:v4.0.10` to `pingcap/pd-enterprise:v4.0.10`. 2. Run the `helm upgrade` command: diff --git a/zh/access-dashboard.md b/zh/access-dashboard.md index 99c09c9f13..d8476c98a2 100644 --- a/zh/access-dashboard.md +++ b/zh/access-dashboard.md @@ -36,7 +36,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/advanced-statefulset.md b/zh/advanced-statefulset.md index 04c55b275e..a3b038530d 100644 --- a/zh/advanced-statefulset.md +++ b/zh/advanced-statefulset.md @@ -77,7 +77,7 @@ kind: TidbCluster metadata: name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: @@ -126,7 +126,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[1]' name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: @@ -177,7 +177,7 @@ metadata: tikv.tidb.pingcap.com/delete-slots: '[]' name: asts spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/configure-a-tidb-cluster.md b/zh/configure-a-tidb-cluster.md index a7907602e1..cf35d02729 100644 --- a/zh/configure-a-tidb-cluster.md +++ b/zh/configure-a-tidb-cluster.md @@ -41,9 +41,9 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/configure-a-tidb-cluster/','/zh/tidb- 相关参数的格式如下： -- `spec.version`，格式为 `imageTag`，例如 `v4.0.9` +- `spec.version`，格式为 `imageTag`，例如 `v4.0.10` - `spec..baseImage`，格式为 `imageName`，例如 `pingcap/tidb` -- `spec..version`，格式为 `imageTag`，例如 `v4.0.9` +- `spec..version`，格式为 `imageTag`，例如 `v4.0.10` ### 推荐配置 @@ -258,7 +258,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.9 + image: pingcap/tidb:v4.0.10 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -280,7 +280,7 @@ metadata: spec: .... tidb: - image: pingcap/tidb:v4.0.9 + image: pingcap/tidb:v4.0.10 imagePullPolicy: IfNotPresent replicas: 1 service: @@ -310,7 +310,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.9 + image: pingcap/tikv:v4.0.10 config: {} replicas: 1 requests: @@ -327,7 +327,7 @@ metadata: spec: .... tikv: - image: pingcap/tikv:v4.0.9 + image: pingcap/tikv:v4.0.10 config: | # [storage] # reserve-space = "2MB" @@ -354,7 +354,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.9 + image: pingcap/pd:v4.0.10 config: lease: 3 enable-prevote: true @@ -370,7 +370,7 @@ metadata: spec: ..... pd: - image: pingcap/pd:v4.0.9 + image: pingcap/pd:v4.0.10 config: | lease = 3 enable-prevote = true @@ -466,7 +466,7 @@ kind: TidbCluster metadata: name: basic spec: - version: v4.0.9 + version: v4.0.10 pvReclaimPolicy: Retain discovery: {} pd: diff --git a/zh/deploy-heterogeneous-tidb-cluster.md b/zh/deploy-heterogeneous-tidb-cluster.md index 6e71672160..8cad9121ec 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.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete discovery: {} @@ -94,7 +94,7 @@ spec: version: 6.1.6 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -133,7 +133,7 @@ spec: tlsCluster: enabled: true configUpdateStrategy: RollingUpdate - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete discovery: {} diff --git a/zh/deploy-on-gcp-gke.md b/zh/deploy-on-gcp-gke.md index dadf8b7f23..14269a9e27 100644 --- a/zh/deploy-on-gcp-gke.md +++ b/zh/deploy-on-gcp-gke.md @@ -193,7 +193,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.9 TiDB Server (Apache License 2.0) Community Edition, MySQL 5.7 compatible + Server version: 5.7.25-TiDB-v4.0.10 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 a4270f44b8..6bff23ee89 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/dev/deploy-on-general-kubernetes/'] 如果服务器没有外网，需要在有外网的机器上将 TiDB 集群用到的 Docker 镜像下载下来并上传到服务器上，然后使用 `docker load` 将 Docker 镜像安装到服务器上。 - 部署一套 TiDB 集群会用到下面这些 Docker 镜像（假设 TiDB 集群的版本是 v4.0.9）： + 部署一套 TiDB 集群会用到下面这些 Docker 镜像（假设 TiDB 集群的版本是 v4.0.10）： ```shell - 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/pd:v4.0.10 + pingcap/tikv:v4.0.10 + pingcap/tidb:v4.0.10 + pingcap/tidb-binlog:v4.0.10 + pingcap/ticdc:v4.0.10 + pingcap/tiflash:v4.0.10 pingcap/tidb-monitor-reloader:v1.0.1 - pingcap/tidb-monitor-initializer:v4.0.9 + pingcap/tidb-monitor-initializer:v4.0.10 grafana/grafana:6.0.1 prom/prometheus:v2.18.1 busybox:1.26.2 @@ -64,26 +64,26 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/deploy-on-general-kubernetes/'] {{< copyable "shell-regular" >}} ```shell - 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/pd:v4.0.10 + docker pull pingcap/tikv:v4.0.10 + docker pull pingcap/tidb:v4.0.10 + docker pull pingcap/tidb-binlog:v4.0.10 + docker pull pingcap/ticdc:v4.0.10 + docker pull pingcap/tiflash:v4.0.10 docker pull pingcap/tidb-monitor-reloader:v1.0.1 - docker pull pingcap/tidb-monitor-initializer:v4.0.9 + docker pull pingcap/tidb-monitor-initializer:v4.0.10 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.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 pd-v4.0.10.tar pingcap/pd:v4.0.10 + docker save -o tikv-v4.0.10.tar pingcap/tikv:v4.0.10 + docker save -o tidb-v4.0.10.tar pingcap/tidb:v4.0.10 + docker save -o tidb-binlog-v4.0.10.tar pingcap/tidb-binlog:v4.0.10 + docker save -o ticdc-v4.0.10.tar pingcap/ticdc:v4.0.10 + docker save -o tiflash-v4.0.10.tar pingcap/tiflash:v4.0.10 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.9.tar pingcap/tidb-monitor-initializer:v4.0.9 + docker save -o tidb-monitor-initializer-v4.0.10.tar pingcap/tidb-monitor-initializer:v4.0.10 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/dev/deploy-on-general-kubernetes/'] {{< copyable "shell-regular" >}} ```shell - 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 pd-v4.0.10.tar + docker load -i tikv-v4.0.10.tar + docker load -i tidb-v4.0.10.tar + docker load -i tidb-binlog-v4.0.10.tar + docker load -i ticdc-v4.0.10.tar + docker load -i tiflash-v4.0.10.tar docker load -i tidb-monitor-reloader-v1.0.1.tar - docker load -i tidb-monitor-initializer-v4.0.9.tar + docker load -i tidb-monitor-initializer-v4.0.10.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 58c1c90b06..8226b9deba 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.9 + version: v4.0.10 replicas: 1 storageClassName: local-storage requests: @@ -45,7 +45,7 @@ spec ... pump: baseImage: pingcap/tidb-binlog - version: v4.0.9 + version: v4.0.10 replicas: 1 storageClassName: local-storage requests: @@ -192,7 +192,7 @@ spec: ```yaml clusterName: example-tidb - clusterVersion: v4.0.9 + clusterVersion: v4.0.10 baseImage: pingcap/tidb-binlog storageClassName: local-storage storage: 10Gi @@ -222,7 +222,7 @@ spec: ```yaml ... - clusterVersion: v4.0.9 + clusterVersion: v4.0.10 baseImage: pingcap/tidb-binlog-enterprise ... ``` diff --git a/zh/deploy-tidb-cluster-across-multiple-kubernetes.md b/zh/deploy-tidb-cluster-across-multiple-kubernetes.md index 801e128b99..a5893a4e0b 100644 --- a/zh/deploy-tidb-cluster-across-multiple-kubernetes.md +++ b/zh/deploy-tidb-cluster-across-multiple-kubernetes.md @@ -58,7 +58,7 @@ kind: TidbCluster metadata: name: "${cluster1_name}" spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete enableDynamicConfiguration: true @@ -115,7 +115,7 @@ kind: TidbCluster metadata: name: "${cluster2_name}" spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete enableDynamicConfiguration: true @@ -440,7 +440,7 @@ kind: TidbCluster metadata: name: "${cluster1_name}" spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC tlsCluster: enabled: true @@ -510,7 +510,7 @@ kind: TidbCluster metadata: name: "${cluster2_name}" spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC tlsCluster: enabled: true diff --git a/zh/deploy-tidb-enterprise-edition.md b/zh/deploy-tidb-enterprise-edition.md index becfe26a1f..b3a3d120c0 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.9 + version: v4.0.10 ... pd: baseImage: pingcap/pd-enterprise @@ -52,7 +52,7 @@ TiDB Operator 会自动通过滚动升级的方式将集群镜像更新为企业 ```yaml spec: - version: v4.0.9 + version: v4.0.10 ... pd: baseImage: pingcap/pd diff --git a/zh/enable-tls-between-components.md b/zh/enable-tls-between-components.md index a857b8e14d..8fa3817676 100644 --- a/zh/enable-tls-between-components.md +++ b/zh/enable-tls-between-components.md @@ -1291,7 +1291,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/enable-tls-between-components/'] spec: tlsCluster: enabled: true - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Retain pd: @@ -1347,7 +1347,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/enable-tls-between-components/'] version: 6.0.1 initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 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 4b885f9c38..81fc78fe66 100644 --- a/zh/enable-tls-for-mysql-client.md +++ b/zh/enable-tls-for-mysql-client.md @@ -529,7 +529,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/enable-tls-for-mysql-client/'] name: ${cluster_name} namespace: ${namespace} spec: - version: v4.0.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Retain pd: diff --git a/zh/monitor-a-tidb-cluster.md b/zh/monitor-a-tidb-cluster.md index 60826bd13b..a3a61baac4 100644 --- a/zh/monitor-a-tidb-cluster.md +++ b/zh/monitor-a-tidb-cluster.md @@ -48,7 +48,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -156,7 +156,7 @@ spec: type: NodePort initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -208,7 +208,7 @@ spec: foo: "bar" initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 reloader: baseImage: pingcap/tidb-monitor-reloader version: v1.0.1 @@ -245,7 +245,7 @@ spec: type: ClusterIP initializer: baseImage: pingcap/tidb-monitor-initializer - version: v4.0.9 + version: v4.0.10 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 e3c1a53c3e..f021881a85 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.9 + version: v4.0.10 replicas: 1 storageClassName: local-storage requests: diff --git a/zh/pd-recover.md b/zh/pd-recover.md index c5f6a31e91..360dcc1ed0 100644 --- a/zh/pd-recover.md +++ b/zh/pd-recover.md @@ -18,7 +18,7 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/pd-recover/'] wget https://download.pingcap.org/tidb-${version}-linux-amd64.tar.gz ``` - `${version}` 是 TiDB 集群版本，例如，`v4.0.9`。 + `${version}` 是 TiDB 集群版本，例如，`v4.0.10`。 2. 解压安装包： diff --git a/zh/restart-a-tidb-cluster.md b/zh/restart-a-tidb-cluster.md index 75dbb4fe38..f19c566fee 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.9 + version: v4.0.10 timezone: UTC pvReclaimPolicy: Delete pd: diff --git a/zh/restore-data-using-tidb-lightning.md b/zh/restore-data-using-tidb-lightning.md index 649e770df0..7c6b8b8bdf 100644 --- a/zh/restore-data-using-tidb-lightning.md +++ b/zh/restore-data-using-tidb-lightning.md @@ -50,7 +50,7 @@ TiDB Lightning 包含两个组件：tidb-lightning 和 tikv-importer。在 Kuber ```yaml clusterName: demo - image: pingcap/tidb-lightning:v4.0.9 + image: pingcap/tidb-lightning:v4.0.10 imagePullPolicy: IfNotPresent storageClassName: local-storage storage: 20Gi diff --git a/zh/upgrade-a-tidb-cluster.md b/zh/upgrade-a-tidb-cluster.md index 30d3f6a62c..a84000e408 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/dev/upgrade-a-tidb-cluster/'] `version` 字段格式如下： - - `spec.version`，格式为 `imageTag`，例如 `v4.0.9` + - `spec.version`，格式为 `imageTag`，例如 `v4.0.10` - `spec..version`，格式为 `imageTag`，例如 `v3.1.0` {{< copyable "shell-regular" >}} @@ -130,7 +130,7 @@ kubectl annotate --overwrite tc ${cluster_name} -n ${namespace} tidb.pingcap.com > > 如果需要升级到企业版，需要把 `.image` 的值改为企业版镜像。 > -> 例如将 `pd.image` 从 `pingcap/pd:v4.0.9` 修改为 `pingcap/pd-enterprise:v4.0.9`。 +> 例如将 `pd.image` 从 `pingcap/pd:v4.0.10` 修改为 `pingcap/pd-enterprise:v4.0.10`。 ### 强制升级 TiDB 集群