v1.2 en, zh: remove the auto scaling doc (#2631)

pingcap · Sep 14, 2024 · 551f46a · 551f46a
1 parent e67241c
commit 551f46a
Show file tree

Hide file tree

Showing 10 changed files with 4 additions and 462 deletions.
diff --git a/en/TOC.md b/en/TOC.md
@@ -50,7 +50,6 @@
     - [Run Containers as a Non-root User](containers-run-as-non-root-user.md)
   - Scale
     - [Manually Scale](scale-a-tidb-cluster.md)
-    - [Automatically Scale](enable-tidb-cluster-auto-scaling.md)
   - Upgrade
     - [Upgrade a TiDB Cluster](upgrade-a-tidb-cluster.md)
     - Upgrade TiDB Operator

diff --git a/en/enable-admission-webhook.md b/en/enable-admission-webhook.md
@@ -246,16 +246,6 @@ TiDB Operator implements many functions using the admission controller. This sec
 
     For example, regarding `TidbCluster` resources, the admission controller for TiDB Operator resources validation checks the required fields of the `spec` field. When you create or update `TidbCluster`, if the check is not passed (for example, neither of the `spec.pd.image` filed and the `spec.pd.baseImage` field is defined), this admission controller refuses the request.
 
-* Admission controller for Pod modification
-
-    The admission controller for Pod modification supports the hotspot scheduling of TiKV in the auto-scaling scenario. To [enable TidbCluster auto-scaling](enable-tidb-cluster-auto-scaling.md), you need to enable this controller. The component is enabled by default if the admission controller is enabled.
-
-    ```yaml
-    admissionWebhook:
-      mutation:
-        pods: true
-    ```
-
 * Admission controller for TiDB Operator resources modification
 
     The admission controller for TiDB Operator resources modification supports filling in the default values of customized resources, such as `TidbCluster` and `TidbMonitor` in TiDB Operator. The component is enabled by default if the admission controller is enabled.

diff --git a/en/enable-tidb-cluster-auto-scaling.md b/en/enable-tidb-cluster-auto-scaling.md
diff --git a/en/tidb-operator-overview.md b/en/tidb-operator-overview.md
@@ -1,6 +1,7 @@
 ---
 title: TiDB Operator Overview
 summary: Learn the overview of TiDB Operator.
+aliases: ['/tidb-in-kubernetes/v1.2/enable-tidb-cluster-auto-scaling']
 ---
 
 # TiDB Operator Overview

diff --git a/en/whats-new-in-v1.1.md b/en/whats-new-in-v1.1.md
@@ -39,7 +39,7 @@ TiDB Operator 1.1 also makes improvements in usability, providing the user exper
 
 ## Experimental features
 
-- Add `TidbClusterAutoScaler` to implement [auto-scaling](enable-tidb-cluster-auto-scaling.md). You can enable this feature by turning on the `AutoScaling` switch.
+- Add `TidbClusterAutoScaler` to implement auto-scaling. You can enable this feature by turning on the `AutoScaling` switch.
 
 - Add the optional [Advanced StatefulSet Controller](advanced-statefulset.md), which supports deleting a specific Pod. You can enable this feature by turning on the `AdvancedStatefulSet` switch.
 

diff --git a/zh/TOC.md b/zh/TOC.md
@@ -50,7 +50,6 @@
     - [以非 root 用户运行](containers-run-as-non-root-user.md)
   - 扩缩容
     - [手动扩缩容](scale-a-tidb-cluster.md)
-    - [自动弹性伸缩](enable-tidb-cluster-auto-scaling.md)
   - 升级
     - [升级 TiDB 集群](upgrade-a-tidb-cluster.md)
     - 升级 TiDB Operator

diff --git a/zh/enable-admission-webhook.md b/zh/enable-admission-webhook.md
@@ -242,16 +242,6 @@ TiDB Operator 通过准入控制器的帮助实现了许多功能。我们将在
 
     举个例子，对于 `TidbCluster` 资源，TiDB Operator 资源验证准入控制器将会检查其 `spec` 字段中的必要字段。如果在 `TidbCluster` 创建或者更新时发现检查不通过，比如同时没有定义 `spec.pd.image` 或者 `spec.pd.baseImage` 字段，TiDB Operator 资源验证准入控制器将会拒绝这个请求。
 
-* Pod 修改准入控制器:
-
-    Pod 修改准入控制器帮助我们在弹性伸缩场景下实现 TiKV 的热点调度功能，在[启用 TidbCluster 弹性伸缩](enable-tidb-cluster-auto-scaling.md)中需要开启该控制器。该组件在准入控制器开启的情况下默认开启。
-
-    ```yaml
-    admissionWebhook:
-      mutation:
-        pods: true
-    ```
-
 * TiDB Operator 资源修改准入控制器:
 
     TiDB Operator 资源修改准入控制器帮助我们实现 TiDB Operator 相关自定义资源的默认值填充工作，如 `TidbCluster`，`TidbMonitor` 等。该组件在准入控制器开启的情况下默认开启。