Automation Suite on Linux installation guide

In-cluster Redis High Availability Add-on configuration​

1. Purchase an HAA license. Contact UiPath® for details.
2. Update the following fields in the cluster_config.json file:
   • fabric.redis.license - enter the HAA license converted to a single base64 string. You need to encode the entire license key to base64, including the text -----LICENSE START----- and -----LICENSE END-----. In bash, you can do that using the following command:
     assignment

     echo '-----LICENSE START-----<license_key_here>-----LICENSE END-----' | base64 -w0
     echo '-----LICENSE START-----<license_key_here>-----LICENSE END-----' | base64 -w0
     

   • fabric.redis.ha - use true to enable HAA and make sure to also configure the fabric.redis.license parameter. This enables HAA database replication and increases the number of HAA pods to 3. By default, fabric.redis.ha is set to false.
     Note:

     If redis.ha is enabled, redis.license needs to be set to a license that supports more than two shards.

     assignment

     "fabric": {
         "redis": { 
             "ha": "true",
             "license": "Base64String" // Replace Base64String with the encoded full license string.
         }
     }
     "fabric": {
         "redis": { 
             "ha": "true",
             "license": "Base64String" // Replace Base64String with the encoded full license string.
         }
     }
     

3. Rerun the fabric installer:
   assignment

   ./install-uipath.sh -i cluster_config.json -f -o output.json --accept-license-agreement
   ./install-uipath.sh -i cluster_config.json -f -o output.json --accept-license-agreement
   

Updating the Redis license​

1. Set up kubectl and ArgoCD access:

   1. Enable kubectl access on the primary node. See Enabling kubectl for instructions.
   2. Enable access to ArgoCD. See Accessing ArgoCD for instructions.

2. Check the current license status:

   To check the status of the current license, run the following Shell command:

   assignment

   kubectl get rec -n redis-system redis-cluster -o jsonpath='{.status.licenseStatus}' | jq
   kubectl get rec -n redis-system redis-cluster -o jsonpath='{.status.licenseStatus}' | jq
   

   • Clusters deployed after the expiry date of the license included in the installer will show the trial 4-shard license that expires in 30 days, as in the following example:

   

   • Clusters that were already running when the license expired will show the following status:

   

3. Update the existing license:

   1. To update the existing license, run the following Shell command:

      assignment

      kubectl patch application fabric-installer -n argocd \
      --type=json -p '[{"op":"add","path":"/spec/source/helm/parameters/-","value":{"name": "global.redis.license", "value": "<LICENSE_KEY_IN_BASE64>"}}]'
      kubectl patch application fabric-installer -n argocd \
      --type=json -p '[{"op":"add","path":"/spec/source/helm/parameters/-","value":{"name": "global.redis.license", "value": "<LICENSE_KEY_IN_BASE64>"}}]'
      

      

   2. To see if the change was applied, access ArgoCD. See Accessing ArgoCD for instructions.

   3. If the fabric-installer application appears out of sync, and the sync process was not triggered automatically, select the Sync button yourself. This may be happen if you are using an older Automation Suite version.

      

      

      

      Note:

      There is a small delay between the moment the ArgoCD UI shows the app synced and when the Redis operator successfully applies the new license.

   4. To see logs from the Redis operator when it tries to apply the license, run the following command:

      assignment

      kubectl logs -n redis-system --since=300s -l name=redis-enterprise-operator -c redis-enterprise-operator --tail=-1 | grep license
      kubectl logs -n redis-system --since=300s -l name=redis-enterprise-operator -c redis-enterprise-operator --tail=-1 | grep license
      

      

   5. If you try to apply an expired license, or you run the installer that ships with an expired license, you will get the following output:

      

   6. To update the Redis license used by older installers before running them, update the fabric.redis.license key in the <installer_folder>/defaults.json:

      

4. Check that the new license is applied:

   To check if the new license is applied, run the following Shell command:

   assignment

   kubectl get rec -n redis-system redis-cluster -o jsonpath='{.status.licenseStatus}' | jq
   kubectl get rec -n redis-system redis-cluster -o jsonpath='{.status.licenseStatus}' | jq
   

   In the following image you can see that the Redis cluster switched from the trial 30-day license to a single-shard 10-year license.

   

External High Availability Add-on configuration​

"fabric": {
  "redis": {
    "hostname": "redis_fqdn",
    "password": "credential_to_connect_redis",
    "port": 6380,
    "tls": true,
  }
}
"fabric": {
  "redis": {
    "hostname": "redis_fqdn",
    "password": "credential_to_connect_redis",
    "port": 6380,
    "tls": true,
  }
}