From a56955335fc3756945827ff47aeb358299306dec Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Mon, 25 Mar 2024 11:34:03 +0800 Subject: [PATCH] fix format issues --- en/configure-a-tidb-cluster.md | 4 ++-- en/deploy-tidb-cluster-across-multiple-kubernetes.md | 2 +- en/enable-tls-between-components.md | 4 ++-- en/get-started.md | 2 +- en/scale-a-tidb-cluster.md | 2 +- en/suspend-tidb-cluster.md | 2 +- en/upgrade-a-tidb-cluster.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/en/configure-a-tidb-cluster.md b/en/configure-a-tidb-cluster.md index 420dda353..4af28ffaa 100644 --- a/en/configure-a-tidb-cluster.md +++ b/en/configure-a-tidb-cluster.md @@ -280,7 +280,7 @@ The deployed cluster topology by default has three PD Pods, three TiKV Pods, and #### Enable PD microservices -> **Notes:** +> **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). @@ -439,7 +439,7 @@ For all the configurable parameters of PD, refer to [PD Configuration File](http ##### Configure PD microservices -> **Notes:** +> **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). diff --git a/en/deploy-tidb-cluster-across-multiple-kubernetes.md b/en/deploy-tidb-cluster-across-multiple-kubernetes.md index 4509ee445..4da15990f 100644 --- a/en/deploy-tidb-cluster-across-multiple-kubernetes.md +++ b/en/deploy-tidb-cluster-across-multiple-kubernetes.md @@ -529,7 +529,7 @@ When you need to make a cluster exit from the joined TiDB cluster deployed acros Take the second TidbCluster created in [the last section](#step-2-deploy-the-new-tidbcluster-to-join-the-tidb-cluster) as an example. First, set the number of replicas of PD, TiKV, and TiDB to `0`. If you have enabled other components such as TiFlash, TiCDC, TiProxy, and Pump, set the number of these replicas to `0`: -> **Notes:** +> **Note:** > > Starting from v8.0.0, PD supports the microservice mode. If PD microservices are configured, you also need to set the `replicas` of the corresponding PD microservice component to `0` in the `pdms` configuration. diff --git a/en/enable-tls-between-components.md b/en/enable-tls-between-components.md index e05b8f6b8..7e66d8e6d 100644 --- a/en/enable-tls-between-components.md +++ b/en/enable-tls-between-components.md @@ -162,7 +162,7 @@ This section describes how to issue certificates using two methods: `cfssl` and ... ``` - > **Notes:** + > **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). To deploy PD microservices in your cluster, it is unnecessary to generate certificates for each component of PD microservices. Instead, you only need to add the host configurations for microservices to the `hosts` field of the `pd-server.json` file. Taking the `scheduling` microservice as an example, you need to configure the following items: > @@ -1470,7 +1470,7 @@ In this step, you need to perform the following operations: Execute `kubectl apply -f tidb-cluster.yaml` to create a TiDB cluster. - > **Notes:** + > **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). To deploy PD microservices, you need to configure `cert-allowed-cn` for each microservice. Taking the Scheduling service as an example, you need to make the following configurations: > diff --git a/en/get-started.md b/en/get-started.md index 7e68867cc..ef214e4b3 100644 --- a/en/get-started.md +++ b/en/get-started.md @@ -297,7 +297,7 @@ tidbcluster.pingcap.com/basic created If you need to deploy a TiDB cluster on an ARM64 machine, refer to [Deploying a TiDB Cluster on ARM64 Machines](deploy-cluster-on-arm64.md). -> **Notes:** +> **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). To deploy PD microservices, use the following command: > diff --git a/en/scale-a-tidb-cluster.md b/en/scale-a-tidb-cluster.md index c4d069f73..805326152 100644 --- a/en/scale-a-tidb-cluster.md +++ b/en/scale-a-tidb-cluster.md @@ -192,7 +192,7 @@ When all Pods are rebuilt and in the `Running` state, the vertical scaling is co ### Scale PD microservice components -> **Notes:** +> **Note:** > > Starting from v8.0.0, PD supports the [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental). diff --git a/en/suspend-tidb-cluster.md b/en/suspend-tidb-cluster.md index c0088de42..bc44ce0de 100644 --- a/en/suspend-tidb-cluster.md +++ b/en/suspend-tidb-cluster.md @@ -62,7 +62,7 @@ If you need to suspend the TiDB cluster, take the following steps: * TiProxy * PD -> **Notes:** +> **Note:** > > If [PD microservices](https://docs.pingcap.com/tidb/dev/pd-microservices) (introduced in TiDB v8.0.0) are deployed in a cluster, the Pods of PD microservices are deleted after the PD Pods are deleted. diff --git a/en/upgrade-a-tidb-cluster.md b/en/upgrade-a-tidb-cluster.md index bffd3b363..31a81774a 100644 --- a/en/upgrade-a-tidb-cluster.md +++ b/en/upgrade-a-tidb-cluster.md @@ -16,7 +16,7 @@ Kubernetes provides the [rolling update](https://kubernetes.io/docs/tutorials/ku When you perform a rolling update, TiDB Operator serially deletes an old Pod and creates the corresponding new Pod in the order of PD, TiProxy, TiFlash, TiKV, and TiDB. After the new Pod runs normally, TiDB Operator proceeds with the next Pod. -> **Notes:** +> **Note:** > > If [PD microservices](https://docs.pingcap.com/tidb/dev/pd-microservices) (introduced in TiDB v8.0.0) are deployed in a cluster, when you perform a rolling update to upgrade the cluster, TiDB Operator serially deletes an old Pod and creates the corresponding new Pod in the order of each PD microservice component, PD, TiKV, and TiDB. After the new Pod runs normally, TiDB Operator proceeds with the next Pod.