Step 3: Post-deployment Steps

Important: You can currently use the GCP deployment template only with Automation Suite 2023.10. We therefore recommend referring to the Automation Suite 2023.10 documentation.

This page walks your through the steps you need to take to access and manage Automation Suite after the deployment has completed.

Updating Certificates

Important:

The installation process generates self-signed certificates on your behalf. These certificates will expire in 90 days, and you must replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes. If you do not update the certificates, the installation will stop working after 90 days.

For instructions, see Managing certificates.

Accessing the deployment outputs

To get the deployment outputs, take the following steps:

Open a terminal.
Go to the directory from which you ran the deployment commands.
Execute the following command:
```
terraform outputterraform output
```

The output should look similar to the following image:

Output definitions

The outputs give you the necessary information for accessing the suite and the cluster.

The following table describes the values:

Key	Description
`fqdn`	The fully qualified domain name provided for the installation. Make sure you use the same one when configuring the DNS. For instructions on how to configure the DNS, see: Configuring the DNS in a single-node evaluation setup Configuring the DNS in a multi-node HA-ready production setup
`lb_ip`	The load balancer’s IP address used for configuring the DNS.
`bastion_ip`	The IP address of the bastion VM needed to access the cluster via SSH.
`deployment_id`	The deployment ID included in the name of all the resources in a deployment.
`db_credentials`	The URL to the secret containing the credentials for the database.
`as_host_credentials`	The URL to the secret containing the credentials for the Host organization in the Automation Suite portal.
`as_default_credentials`	The URL to the secret containing the credentials for the Host organization in the Automation Suite portal.
`argocd_credentials`	The URL to the secret containing the credentials for the ArgoCD console used to manage the installed products.

Accessing the services

To access the services, you must have a DNS configured. See Configuring the DNS in a single-node evaluation setup or Configuring the DNS in a multi-node HA-ready production setup for details.

Alternatively, you can follow the instructions in Configuring a client machine to access the cluster for testing purposes only.

If using a self-signed certificate, you may get an certificate error as shown in the following image.

Click Proceed to…, then update the cluster certificates as explained in Configuring the certificates in a single-node evaluation setup or Configuring the certificates in a multi-node HA-ready production setup.

Accessing Automation Suite portal

You can access the Automation Suite portal at https://<fqdn>. You can get the credentials via a secret available at:

as_host_credentials URL for the Host organization;
as_default_credentials URL for the Default organization.

Accessing ArgoCD

You can access the ArgoCD console at https://alm.<fqdn>. You can get the credentials via a secret that can be found at the argocd_credentials URL.

Accessing Rancher

You can access the Monitoring console at htpps://monitoring.<fqdn> . The username is admin, and the password can be obtained as follows:

Connect to any of the server nodes by SSH (bastion_ip can be found in the deployment outputs):

ssh -i <path_to_private_key> <username>@<bastion_ip>ssh -i <path_to_private_key> <username>@<bastion_ip>

Run the following commands on the node:

sudo su
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get secrets/rancher-admin-password -n cattle-system -o "jsonpath={.data['password']}" | base64 -dsudo su
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get secrets/rancher-admin-password -n cattle-system -o "jsonpath={.data['password']}" | base64 -d

Accessing the cluster

Open a terminal and use SSH to connect to bastion. You can find bastion_ip in the deployment outputs.
```
ssh -i <path_to_private_key> <username>@<bastion_ip>ssh -i <path_to_private_key> <username>@<bastion_ip>
```
From bastion, you can access other nodes via SSH using the following command. The username must be the same as the one used to connect to bastion. You can find the <node_address> in the GCP console, in the column Internal IP.
```
ssh -i .ssh/private_key <username>@<node_address>ssh -i .ssh/private_key <username>@<node_address>
```

You should see the following dashboard showing the state of the cluster:

Editing the number of nodes

Use the GPC console to edit number of nodes (server or agent nodes) as follows:

In the Instance Group tab, search for the MIGs, and click on the one corresponding to the node type you want to modify.
Click Edit.
Modify the Number of instances field according to your needs, and click Save.