diff --git a/en/initialize-a-cluster.md b/en/initialize-a-cluster.md index fb8bcf63dd5..0b75a0e3763 100644 --- a/en/initialize-a-cluster.md +++ b/en/initialize-a-cluster.md @@ -13,7 +13,7 @@ This document describes how to initialize a TiDB cluster in Kubernetes (K8s), sp > - After creating the TiDB cluster, if you manually change the password of the `root` account, the initialization will fail. > - The following steps apply only when you have created a cluster for the first time. Further configuration or modification after the initial cluster creation is not valid. -## Step 1: Configure TidbInitializer +## Configure TidbInitializer Refer to [TidbInitializer example](https://github.com/pingcap/tidb-operator/blob/master/manifests/initializer/tidb-initializer.yaml), [API documentation](api-references.md), and the following steps to complete TidbInitializer Custom Resource (CR), and save it to the `${cluster_name}/tidb-initializer.yaml` file. Please switch the TidbInitializer example and API documentation to the currently used version of TiDB Operator. @@ -39,11 +39,11 @@ When a cluster is created, a default account `root` is created with no password. This command creates `root` and `developer` users with their passwords, which are saved in the `tidb-secret` object. By default, the regular `developer` user is only granted with the `USAGE` privilege. You can set other privileges in the `initSql` configuration item. -## Step 2: Set a host that has access to TiDB +## Set a host that has access to TiDB To set a host that has access to TiDB, modify the `permitHost: ${mysql_client_host_name}` configuration item in `${cluster_name}/tidb-initializer.yaml`. If it is not set, all hosts have access to TiDB. For details, refer to [Mysql GRANT host name](https://dev.mysql.com/doc/refman/5.7/en/grant.html). -## Step 3: Initialize SQL statements in batch +## Initialize SQL statements in batch The cluster can also automatically execute the SQL statements in batch in `initSql` during the initialization. This function can be used to create some databases or tables for the cluster and perform user privilege management operations. @@ -63,7 +63,7 @@ initSql: |- > > Currently no verification has been implemented for `initSql`. You can create accounts and set passwords in `initSql`, but it is not recommended to do so because passwords created this way are saved as plaintext in the initializer job object. -## Step 4: Initialize the cluster +## Initialize the cluster {{< copyable "shell-regular" >}}