update MD by dispatch event pingcap/docs-tidb-operator release-1.6

Author: github-actions

markdown-pages/en/tidb-in-kubernetes/release-1.6/deploy-tidb-binlog.md

@@ -5,7 +5,7 @@ summary: Learn how to deploy TiDB Binlog for a TiDB cluster on Kubernetes.
 
 # Deploy TiDB Binlog
 
-This document describes how to maintain [TiDB Binlog](https://docs.pingcap.com/tidb/stable/tidb-binlog-overview) of a TiDB cluster on Kubernetes.
+This document describes how to maintain [TiDB Binlog](https://docs.pingcap.com/tidb/v8.1/tidb-binlog-overview) of a TiDB cluster on Kubernetes.
 
 > **Warning:**
 >
@@ -287,7 +287,7 @@ If you set the downstream database of `tidb-drainer` to `mysql/tidb`, and if you
 
 ## Remove Pump/Drainer nodes
 
-For details on how to maintain the node state of the TiDB Binlog cluster, refer to [Starting and exiting a Pump or Drainer process](https://docs.pingcap.com/tidb/stable/maintain-tidb-binlog-cluster#starting-and-exiting-a-pump-or-drainer-process).
+For details on how to maintain the node state of the TiDB Binlog cluster, refer to [Starting and exiting a Pump or Drainer process](https://docs.pingcap.com/tidb/v8.1/maintain-tidb-binlog-cluster#starting-and-exiting-a-pump-or-drainer-process).
 
 If you want to remove the TiDB Binlog component completely, it is recommended that you first remove Pump nodes and then remove Drainer nodes.
 

markdown-pages/en/tidb-in-kubernetes/release-1.6/migrate-tidb-to-kubernetes.md

@@ -83,7 +83,7 @@ Remove all TiDB nodes of the source cluster:
 
 - If the source cluster is deployed using TiUP, refer to [Scale in a TiDB/PD/TiKV cluster](https://docs.pingcap.com/tidb/stable/scale-tidb-using-tiup#scale-in-a-tidbpdtikv-cluster).
 
-- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a TiDB node](https://docs.pingcap.com/tidb/stable/scale-tidb-using-ansible#decrease-the-capacity-of-a-tidb-node).
+- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a TiDB node](https://docs-archive.pingcap.com/tidb/v4.0/scale-tidb-using-ansible#decrease-the-capacity-of-a-tidb-node).
 
 > **Note:**
 >
@@ -95,7 +95,7 @@ Remove all TiKV nodes of the source cluster:
 
 - If the source cluster is deployed using TiUP, refer to [Scale in a TiDB/PD/TiKV cluster](https://docs.pingcap.com/tidb/stable/scale-tidb-using-tiup#scale-in-a-tidbpdtikv-cluster).
 
-- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a TiKV node](https://docs.pingcap.com/tidb/stable/scale-tidb-using-ansible#decrease-the-capacity-of-a-tikv-node).
+- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a TiKV node](https://docs-archive.pingcap.com/tidb/v4.0/scale-tidb-using-ansible#decrease-the-capacity-of-a-tikv-node).
 
 > **Note:**
 >
@@ -108,7 +108,7 @@ Remove all PD nodes of the source cluster:
 
 - If the source cluster is deployed using TiUP, refer to [Scale in a TiDB/PD/TiKV cluster](https://docs.pingcap.com/tidb/stable/scale-tidb-using-tiup#scale-in-a-tidbpdtikv-cluster).
 
-- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a PD node](https://docs.pingcap.com/tidb/stable/scale-tidb-using-ansible#decrease-the-capacity-of-a-pd-node).
+- If the source cluster is deployed using TiDB Ansible, refer to [Decrease the capacity of a PD node](https://docs-archive.pingcap.com/tidb/v4.0/scale-tidb-using-ansible#decrease-the-capacity-of-a-pd-node).
 
 ## Step 6: Delete the `spec.pdAddresses` field
 

markdown-pages/zh/tidb-in-kubernetes/release-1.6/deploy-tidb-binlog.md

@@ -5,7 +5,7 @@ summary: 了解如何在 Kubernetes 上部署 TiDB 集群的 TiDB Binlog。
 
 # 部署 TiDB Binlog
 
-本文档介绍如何在 Kubernetes 上部署 TiDB 集群的 [TiDB Binlog](https://docs.pingcap.com/zh/tidb/stable/tidb-binlog-overview)。
+本文档介绍如何在 Kubernetes 上部署 TiDB 集群的 [TiDB Binlog](https://docs.pingcap.com/zh/tidb/v8.1/tidb-binlog-overview)。
 
 > **警告：**
 >
@@ -281,7 +281,7 @@ tlsSyncer: {}
 
 ## 缩容/移除 Pump/Drainer 节点
 
-如需详细了解如何维护 TiDB Binlog 集群节点状态信息，可以参考 [Pump/Drainer 的启动、退出流程](https://docs.pingcap.com/zh/tidb/stable/maintain-tidb-binlog-cluster#pumpdrainer-的启动退出流程)。
+如需详细了解如何维护 TiDB Binlog 集群节点状态信息，可以参考 [Pump/Drainer 的启动、退出流程](https://docs.pingcap.com/zh/tidb/v8.1/maintain-tidb-binlog-cluster#pumpdrainer-的启动退出流程)。
 
 如果需要完整移除 TiDB Binlog 组件，最好是先移除 Pump 节点，再移除 Drainer 节点。
 

markdown-pages/zh/tidb-in-kubernetes/release-1.6/migrate-tidb-to-kubernetes.md

@@ -82,7 +82,7 @@ summary: 介绍如何将部署在物理机或虚拟机中的 TiDB 迁移至 Kube
 将待迁移集群的 TiDB 节点缩容至 0 个：
 
 - 如果待迁移集群使用 TiUP 部署，参考[缩容 TiDB/PD/TiKV 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-tiup#缩容-tidbpdtikv-节点)一节。
-- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 TiDB 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-ansible#缩容-tidb-节点)一节。
+- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 TiDB 节点](https://docs-archive.pingcap.com/zh/tidb/v4.0/scale-tidb-using-ansible#缩容-tidb-节点)一节。
 
 > **注意：**
 >
@@ -93,7 +93,7 @@ summary: 介绍如何将部署在物理机或虚拟机中的 TiDB 迁移至 Kube
 将待迁移集群的 TiKV 节点缩容至 0 个：
 
 - 如果待迁移集群使用 TiUP 部署，参考[缩容 TiDB/PD/TiKV 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-tiup#缩容-tidbpdtikv-节点)一节。
-- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 TiKV 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-ansible#缩容-tikv-节点)一节。
+- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 TiKV 节点](https://docs-archive.pingcap.com/zh/tidb/v4.0/scale-tidb-using-ansible#缩容-tikv-节点)一节。
 
 > **注意：**
 >
@@ -105,7 +105,7 @@ summary: 介绍如何将部署在物理机或虚拟机中的 TiDB 迁移至 Kube
 将待迁移集群的 PD 节点缩容至 0 个：
 
 - 如果待迁移集群使用 TiUP 部署，参考[缩容 TiDB/PD/TiKV 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-tiup#缩容-tidbpdtikv-节点)一节。
-- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 PD 节点](https://docs.pingcap.com/zh/tidb/stable/scale-tidb-using-ansible#缩容-pd-节点)一节。
+- 如果待迁移集群使用 TiDB Ansible 部署，参考[缩容 PD 节点](https://docs-archive.pingcap.com/zh/tidb/v4.0/scale-tidb-using-ansible#缩容-pd-节点)一节。
 
 ## 第六步：删除 `spec.pdAddresses` 字段