pdms: remove pd playground (#16919)

pingcap · Apr 2, 2024 · 88a5d0b · 88a5d0b
1 parent 010f6c2
commit 88a5d0b
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 29 deletions.
diff --git a/pd-microservices.md b/pd-microservices.md
@@ -40,10 +40,7 @@ In addition, when the scheduling module is changed, you can update the `scheduli
 
 ## Usage
 
-Currently, PD microservices can be deployed using TiDB Operator or TiUP Playground.
-
-<SimpleTab>
-<div label="TiDB Operator">
+Currently, PD microservices can be deployed using TiDB Operator.
 
 For detailed information on using TiDB Operator, see the following documents:
 
@@ -52,16 +49,6 @@ For detailed information on using TiDB Operator, see the following documents:
 - [Modify PD microservices](https://docs.pingcap.com/tidb-in-kubernetes/dev/modify-tidb-configuration#modify-pd-microservice-configuration)
 - [Scale PD microservice components](https://docs.pingcap.com/tidb-in-kubernetes/dev/scale-a-tidb-cluster#scale-pd-microservice-components)
 
-</div>
-<div label="TiUP Playground">
-
-For detailed information on using TiUP Playground, see the following document:
-
-- [Deploy PD microservices](/tiup/tiup-playground.md#deploy-pd-microservices)
-
-</div>
-</SimpleTab>
-
 When deploying and using PD microservices, pay attention to the following:
 
 - After you enable microservices and restart PD for a cluster, PD stops allocating TSO for the cluster. Therefore, you need to deploy the `tso` microservice in the cluster when you enable microservices.

diff --git a/releases/release-8.0.0.md b/releases/release-8.0.0.md
@@ -74,7 +74,7 @@ Quick access: [Quick start](https://docs.pingcap.com/tidb/v8.0/quick-start-with-
 
   Each microservice is deployed as an independent process. If you configure more than one replica for a microservice, the microservice automatically implements a primary-secondary fault-tolerant mode to ensure high availability and reliability of the service.
 
-    Currently, PD microservices can only be deployed using TiDB Operator and TiUP playground. It is recommended to consider this mode when PD becomes a significant performance bottleneck that cannot be resolved by scaling up.
+    Currently, PD microservices can only be deployed using TiDB Operator. It is recommended to consider this mode when PD becomes a significant performance bottleneck that cannot be resolved by scaling up.
 
     For more information, see [documentation](/pd-microservices.md).
 

diff --git a/tiup/tiup-playground.md b/tiup/tiup-playground.md
@@ -171,17 +171,4 @@ You can specify a `pid` in the `tiup playground scale-in` command to scale in th
 
 ```shell
 tiup playground scale-in --pid 86526
-```
-
-## Deploy PD microservices
-
-Starting from v8.0.0, PD supports the [microservice mode](/pd-microservices.md) (experimental). You can deploy the `tso` microservice and `scheduling` microservice for your cluster using TiUP Playground as follows:
-
-```shell
-tiup playground v8.0.0 --pd.mode ms --pd.api 3 --pd.tso 2 --pd.scheduling 3
-```
-
-- `--pd.mode`: setting it to `ms` means enabling the microservice mode for PD.
-- `--pd.api num`: specifies the number of APIs for PD microservices. It must be at least `1`.
-- `--pd.tso num`: specifies the number of instances to be deployed for the `tso` microservice.
-- `--pd.scheduling num`: specifies the number of instances to be deployed for the `scheduling` microservice.
+```