Verifying the deployment

Verifying the RKE2 and Rancher deployment

Verify if you are able to log in to the Rancher UI using the username and password you configured at the time of deployment.
In the Rancher UI, validate if the Rancher cluster is listed in Clusters table with the name local at the home page.
Verify if all the attached nodes to the cluster are up and running by following the steps given below.
1. In the Rancher UI, click the menu icon at the top left corner, and then click Local.
2. Click Nodes.
3. Verify if all the nodes are in Active state and the roles assigned to each of them is set to Control Plane, Etcd.
Check the status of the Rancher pods by following the steps given below.
1. In the Rancher UI, click the menu icon at the top left corner, and then click Local.
2. Go to Workload > Pods.
3. In the Namespaces dropdown menu, select cattle-system.
  This lists all the pods in the cattle-system namespace.
4. Validate if all the listed pods are in Running state.

Verifying the deployment of Adeptia Connect application

Validate if the Adeptia Connect helm is deployed.
1. Log in to the Rancher UI.
2. Click the menu icon at the top left corner, and then click Local.
3. Go to Apps > Installed Apps.
4. In the Installed Apps, verify if the chart entry for adeptia-connect is in Deployed state.
Check the status of the deployed pods of adeptia-connect.
1. Log in to the Rancher UI.
2. Click the menu icon at the top left corner, and then click Local.
3. Go to Workload > Pods.
4. In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.
5. Validate if all the listed pods are in Running state.
Check the logs to see the status of the pods by following the steps given below.
1. Follow the steps from a through d.
2. Click the more options icon against the pod whose status you want to view, and then click View Logs.
3. Search for “Microservice started successfully” to validate if the pod was started successfully.
  The screenshot given below is an example that shows the status of the Runtime pod.
  Note: The status of runtime deployment manager and rabbitmq pods could not be viewed in their respective logs.
Follow the steps given below to check the status of the shared Runtime pod.
1. Follow the steps from a through d.
2. Verify if the pod for ac-runtime microservice is present and is in Running state.
Verify if you are able to log in to the Adeptia Connect application.
Verify if the shared NFS volumes are attached with required pods.
1. Log in to the Rancher UI.
2. Click the menu icon at the top left corner, and then click Local.
3. Go to Workload > Deployments.
4. In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.
5. Click the deployment (link in the name column) for which you want to check the mounted volumes.
6. Select Config at the top-right corner.
7. Click Storage.
  A list of all the volumes that are mounted to the pods is displayed.
8. Check if the shared NFS volumes are attached to following pods:
  1. runtime
  2. event
  3. archival and cleanup
  4. portal
  5. webrunner
  6. listener

Verifying the deployment of EFK

Check the status of the EFK services pods'.
1. Log in to the Rancher UI.
2. Click the menu icon at the top left corner, and then click Local.
3. Go to Workload > pods.
4. In the Namespaces dropdown menu, select logging.
5. Verify if all the pods are in Running state.
Verify if you are able to log in to the Kibana UI using the username elastic and the password you configured at the time of deployment.
Verify if the index pattern for all microservices is listed in Kibana UI.
1. Log in to the Kibana UI.
2. Click the menu icon at top left corner.
3. Click Discover.
4. Click the Kibana index pattern dropdown.
5. Verify if the list of all the microservices deployed in adeptia-connect namespace is displayed.

Verify user account id (UID)

Check the allocation of UID “1000“ on cluster nodes.
1. Login into the Jumpbox and access cluster node(VM) using the below command.
```
ssh <nodename/IP>
```
2. View passwd file using the below command and verify the user associated with UID “1000“.
```
sudo cat /etc/passwd
```
  Refer to the below screenshot

The user ID “1000“ must be allocated to a system user or a user who is installing the Rancher package. If UID “1000“ is being used by another user, then refer to the guideline to swap the UID.

Check the Rancher processes running under user ID “1000“ on cluster nodes.
1. Login into the Jumpbox and access cluster node(VM) using the below command.
```
ssh <nodename/IP>
```
2. Check the Rancher processes running as user ID “1000“ using the below command.
```
sudo ps aux | grep <user>
```
3. Identify the processes displayed running as user ID “1000” in the above command result. Refer to the below screenshot.

The Rancher processes can only be allowed to run as a root user or a user having UID 1000.