fix broken links (pingcap#3081) (pingcap#3082)

Author: ti-chi-bot

en/releases/release-2.0.0-beta.0.md

@@ -45,7 +45,7 @@ TiDB Operator v2 includes a comprehensive redesign of the v1 architecture, with
 
 - **Support [CRD subresources](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#subresources)**:
     - Support the `status` subresource for unified status management.
-    - Support the `scale` subresource to integrate with [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/), enabling auto-scaling.
+    - Support the `scale` subresource to integrate with [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/), enabling auto-scaling.
     - Improve compatibility with the Kubernetes ecosystem.
 
 - **Optimize the configuration management**:

en/releases/release-2.0.0.md

@@ -41,7 +41,7 @@ TiDB Operator v2 includes a comprehensive redesign of the v1 architecture, with
 
 - **Support [CRD subresources](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#subresources)**:
     - Support the `status` subresource for unified status management.
-    - Support the `scale` subresource to integrate with [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/), enabling auto-scaling.
+    - Support the `scale` subresource to integrate with [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/), enabling auto-scaling.
     - Improve compatibility with the Kubernetes ecosystem.
 
 - **Support feature gates to control change behavior**:

en/v2-vs-v1.md

@@ -16,7 +16,7 @@ Initially, the TiDB cluster has only three core components: PD, TiKV, and TiDB.
 - The number of TiDB cluster components has increased, with eight components currently defined in the `TidbCluster` CRD.
 - To display status, the state of all nodes is defined in the `TidbCluster` CRD.
 - Heterogeneous clusters are not considered initially, so additional `TidbCluster` CRs has to be introduced to support them.
-- The `/scale` API is not supported, making it impossible to integrate with Kubernetes [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).
+- The `/scale` API is not supported, making it impossible to integrate with Kubernetes [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/).
 - A large CR/CRD can cause difficult-to-resolve performance issues.
 
 TiDB Operator v2 addresses these issues by splitting `TidbCluster` into multiple independent CRDs by component.

zh/releases/release-2.0.0-beta.0.md

@@ -45,7 +45,7 @@ TiDB Operator v2 对 v1 的核心架构进行了全面重构，主要包括：
 
 - **支持 [CRD 子资源](https://kubernetes.io/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#subresources)**：
     - 支持 `status` 子资源，实现统一的状态管理
-    - 支持 `scale` 子资源，可与 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale/) 集成，实现自动扩缩容
+    - 支持 `scale` 子资源，可与 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/) 集成，实现自动扩缩容
     - 增强与 Kubernetes 生态系统的集成能力
 
 - **优化配置管理**：

zh/releases/release-2.0.0.md

@@ -41,7 +41,7 @@ TiDB Operator v2 对 v1 的核心架构进行了全面重构，主要包括：
 
 - **支持 [CRD 子资源](https://kubernetes.io/zh-cn/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#subresources)**：
     - 支持 `status` 子资源，实现统一的状态管理
-    - 支持 `scale` 子资源，可与 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale/) 集成，实现自动扩缩容
+    - 支持 `scale` 子资源，可与 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/) 集成，实现自动扩缩容
     - 增强与 Kubernetes 生态系统的集成能力
 
 - **支持使用 Feature Gates 控制变更行为**：

zh/v2-vs-v1.md

@@ -16,7 +16,7 @@ summary: 介绍 TiDB Operator v2 与 v1 的主要差异。
 - TiDB 集群的组件不断增加，目前已经有 8 个组件定义在 `TidbCluster` CRD 中
 - 为了实现状态展示，所有节点的状态都定义在了 `TidbCluster` CRD 中
 - 缺乏原生对异构集群对支持，只能通过引入额外的 `TidbCluster` CR 实现异构集群
-- 无法支持 `/scale` API，无法与 Kubernetes 的 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale/) 生态集成
+- 无法支持 `/scale` API，无法与 Kubernetes 的 [HorizontalPodAutoscaler (HPA)](https://kubernetes.io/zh-cn/docs/concepts/workloads/autoscaling/horizontal-pod-autoscale/) 生态集成
 - 一个巨大的 CR/CRD 可能带来难以解决的性能问题
 
 为解决上述问题，TiDB Operator v2 将 `TidbCluster` CRD 按组件拆分为多个独立的 CRD。