en,zh; Bump DM to v2.0.3 (#1229)

pingcap · May 28, 2021 · 6300088 · 6300088
1 parent e4591b9
commit 6300088
Show file tree

Hide file tree

Showing 4 changed files with 20 additions and 20 deletions.
diff --git a/en/deploy-tidb-dm.md b/en/deploy-tidb-dm.md
@@ -25,9 +25,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 `v2.0.2`.
+- `spec.version`: the format is `imageTag`, such as `v2.0.3`.
 - `spec.<master/worker>.baseImage`: the format is `imageName`, such as `pingcap/dm`.
-- `spec.<master/worker>.version`: the format is `imageTag`, such as `v2.0.2`.
+- `spec.<master/worker>.version`: the format is `imageTag`, such as `v2.0.3`.
 
 TiDB Operator only supports deploying DM 2.0 and later versions.
 
@@ -46,7 +46,7 @@ metadata:
   name: ${dm_cluster_name}
   namespace: ${namespace}
 spec:
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   master:
@@ -138,27 +138,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 v2.0.2):
+1. Deploy a DM cluster requires the following Docker image (assuming the version of the DM cluster is v2.0.3):
 
     ```shell
-    pingcap/dm:v2.0.2
+    pingcap/dm:v2.0.3
     ```
 
 2. To download the image, execute the following command:
 
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker pull pingcap/dm:v2.0.2
-    docker save -o dm-v2.0.2.tar pingcap/dm:v2.0.2
+    docker pull pingcap/dm:v2.0.3
+    docker save -o dm-v2.0.3.tar pingcap/dm:v2.0.3
     ```
 
 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-v2.0.2.tar
+    docker load -i dm-v2.0.3.tar
     ```
 
 After deploying the DM cluster, execute the following command to view the Pod status:

diff --git a/en/enable-tls-for-dm.md b/en/enable-tls-for-dm.md
@@ -505,7 +505,7 @@ metadata:
 spec:
   tlsCluster:
     enabled: true
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   master:
@@ -573,7 +573,7 @@ metadata:
   name: ${cluster_name}
   namespace: ${namespace}
 spec:
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   tlsClientSecretNames:

diff --git a/zh/deploy-tidb-dm.md b/zh/deploy-tidb-dm.md
@@ -25,9 +25,9 @@ summary: 了解如何在 Kubernetes 上部署 TiDB DM 集群。
 
 相关参数的格式如下：
 
-- `spec.version`，格式为 `imageTag`，例如 `v2.0.2`
+- `spec.version`，格式为 `imageTag`，例如 `v2.0.3`
 - `spec.<master/worker>.baseImage`，格式为 `imageName`，例如 `pingcap/dm`
-- `spec.<master/worker>.version`，格式为 `imageTag`，例如 `v2.0.2`
+- `spec.<master/worker>.version`，格式为 `imageTag`，例如 `v2.0.3`
 
 TiDB Operator 仅支持部署 DM 2.0 及更新版本。
 
@@ -46,7 +46,7 @@ metadata:
   name: ${dm_cluster_name}
   namespace: ${namespace}
 spec:
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   master:
@@ -136,28 +136,28 @@ kubectl apply -f ${dm_cluster_name}.yaml -n ${namespace}
 
 如果服务器没有外网，需要按下述步骤在有外网的机器上将 DM 集群用到的 Docker 镜像下载下来并上传到服务器上，然后使用 `docker load` 将 Docker 镜像安装到服务器上：
 
-1. 部署一套 DM 集群会用到下面这些 Docker 镜像（假设 DM 集群的版本是 v2.0.2）：
+1. 部署一套 DM 集群会用到下面这些 Docker 镜像（假设 DM 集群的版本是 v2.0.3）：
 
     ```shell
-    pingcap/dm:v2.0.2
+    pingcap/dm:v2.0.3
     ```
 
 2. 通过下面的命令将所有这些镜像下载下来：
 
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker pull pingcap/dm:v2.0.2
+    docker pull pingcap/dm:v2.0.3
 
-    docker save -o dm-v2.0.2.tar pingcap/dm:v2.0.2
+    docker save -o dm-v2.0.3.tar pingcap/dm:v2.0.3
     ```
 
 3. 将这些 Docker 镜像上传到服务器上，并执行 `docker load` 将这些 Docker 镜像安装到服务器上：
 
     {{< copyable "shell-regular" >}}
 
     ```shell
-    docker load -i dm-v2.0.2.tar
+    docker load -i dm-v2.0.3.tar
     ```
 
 部署 DM 集群完成后，通过下面命令查看 Pod 状态：

diff --git a/zh/enable-tls-for-dm.md b/zh/enable-tls-for-dm.md
@@ -478,7 +478,7 @@ metadata:
 spec:
   tlsCluster:
     enabled: true
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   master:
@@ -544,7 +544,7 @@ metadata:
   name: ${cluster_name}
   namespace: ${namespace}
 spec:
-  version: v2.0.2
+  version: v2.0.3
   pvReclaimPolicy: Retain
   discovery: {}
   tlsClientSecretNames: