# Deploying with TiUP Step 4 - Execute Deployment Commands

__*TiDB deployment steps*__
__*TiUP deployment command*__

+ Examine the potential risks of the cluster:
  + `tiup cluster check ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]`

+ Potential risks of automated remediation of clusters:
  + `tiup cluster check ./topology.yaml --apply --user root [-p] [-i /home/root/.ssh/gcp_rsa]`

+ Execute the deploy command to deploy the TiDB cluster:
  + `tiup cluster deploy ${cluster-name} v6.1.0 ./topology.yaml --user root [-p] [-i /home/root/.ssh/gcp_rsa]`

-------------------------------------------------------------
Before executing the deploy command, use the check and check —apply commands to check and automatically fix the potential risks of the cluster:
TIUP CLUSTER CHECK. /topology.yaml —user root [-p] [-i /home/root/.ssh/gcp_rsa]
TIUP CLUSTER CHECK. /topology.yaml —apply —user root [-p] [-i /home/root/.ssh/gcp_rsa]

Execute the deploy command to deploy the TiDB cluster:
tiup cluster deploy $ {cluster-name} v6.1.0. /topology.yaml —user root [-p] [-i /home/root/.ssh/gcp_rsa]

In the above deployment command:
- $ {cluster-name} indicates the cluster name of the TiUP cluster deployment.
- You can view the latest available version supported by TiUP by executing tiup list tidb. The rest of the content is v6.1.0 as an example
- The initialization configuration file is topology.yaml
- —user root: Log in to the target host as the root user to complete the cluster deployment. This user needs to have ssh permission to the target machine and sudo privilege on the target machine. You can also use other users with ssh and sudo privilege complete the deployment.
- [-i] and [-p]: This option is not required. If password-free login to the target machine is already configured, it is not required. Otherwise, select one. [-i] is the private key of the root user (or another user specified by —user) that can log in to the target machine, or you can use [-p] to interactively enter the user's password

It is expected that the deployed cluster `${cluster-name}` deployed keyword will appear at the end of the log, indicating that the deployment was successful.