Install DataStore and Agent - EcoSys - 2.0 - Installation & Upgrade - Hexagon PPM

EcoSys Connect Installation and Configuration (Microk8s Kubernetes)

Language
English (United States)
Product
EcoSys
Search by Category
Installation & Upgrade
EcoSys Version
2.0

Once the Config-Server, Dispatcher, and LogAgent are running, the Agent can be installed.

Follow these steps:

  1. Configure the ../../helm/connect-agent/values.yaml and update the settings.

    • Refer to the table from the section 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.

  2. 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.

  3. When the install-agent.sh script completes, it displays a message of ‘STATUS: deployed’. The script deploys Connect Agent into the Kubernetes Cluster, to determine if Connect Agent has started successfully.

  4. Run ‘microk8s kubectl get deployments -n <AGENT_NAMESPACE>’

    There are two deployments – agent and datastore. Each have 1/1 in the Ready Column.

    It can take several minutes for Connect to initialize after starting.

  5. If the deployment status is not correct, run ‘microk8s kubectl get pods -n <AGENT_NAMESPACE>’ to check the status of the pods.


  6. If the pods fail to start, additional log information can be found by running the following:

    microk8s kubectl logs <POD ID> -n <AGENT _NAMESPACE>

    OR

    microk8s kubectl describe pod <POD ID> -n <AGENT _NAMESPACE>

    The <AGENT_NAMESPACE> is the value set for AGENT_NAMESPACE in the env.sh file.

  7. 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.