Once the Config-Server, Dispatcher, and LogAgent are running, the Agent can be installed.
Follow these steps:
-
Configure the ../../helm/connect-agent/values.yaml and update the settings.
-
Refer to the table from Install Config-Server, Dispatcher, and LogAgent to determine the proper settings for each value.
-
If the Agent is being installed in the same cluster as the Dispatcher the same values.yaml can be used.
-
-
Run the ‘./install-agent.sh <parameters>’ to install the Connect Platform. The following are the required parameters:
-
<config-server-password>: the password that Config Server clients will use to retrieve configuration
-
<connect-passphrase>: the passphrase that Connect will use for Password-based Encryption.
-
<datastore-db-password>: the admin user password for the DataStore
-
<datastore-db-backup-password>: the backup user password for the DataStore
-
-
When the install-agent.sh script completes, it displays a message of ‘STATUS: deployed’. The script deploys Connect into the Kubernetes Cluster, to determine if Connect has started successfully.
-
Run ‘kubectl get deployments -n <AGENT_NAMESPACE>’
There are two deployments – config-server, dispatcher and logagent. Each have 1/1 in the Ready Column.
It can take several minutes for Connect to initialize after starting.
-
If the deployment status is not correct, run ‘kubectl get pods -n <AGENT_NAMESPACE>’ to check the status of the pods.
-
If the pods fail to start, additional log information can be found by running the following:
kubectl logs <POD ID> -n <AGENT _NAMESPACE>
OR
kubectl describe pod <POD ID> -n <AGENT _NAMESPACE>
The <AGENT_NAMESPACE> is the value set for AGENT_NAMESPACE in the env.sh file.
-
Make sure to preserve the install and helm folders for future use. These files/settings will be used for restores and upgrades in the future.