Automation Suite on OpenShift installation guide

1. Convert the standalone Automation Suite cluster into the primary cluster. For details, see Converting a standalone cluster into a primary cluster.
2. Install secondary Automation Suite cluster. For details, see Disaster Recovery - Installing the secondary cluster.

Converting a standalone cluster into a primary cluster​

1. Update input.json. Add or update fqdn, cluster_fqdn, and enable multisite.

   assignment

   "fqdn" : "<global traffic manager fqdn>"
   "cluster_fqdn": "<fqdn of the primary cluster>",
   
   "multisite": {
       "enabled": true,
       "primary": true
    }
   "fqdn" : "<global traffic manager fqdn>"
   "cluster_fqdn": "<fqdn of the primary cluster>",
   
   "multisite": {
       "enabled": true,
       "primary": true
    }
   

   For details, see the following documentation: Advanced installation experience.

   Update the TLS certificate section to configure the new certificate, ensuring it meets the requirements outlined in the section.

   Note:

   It is recommended to keep the FQDN of your existing Automation Suite setup to avoid reconfiguring all your robots.

2. Reapply the manifest by running the following command:

   assignment

   uipathctl manifest apply input.json --versions versions.json
   uipathctl manifest apply input.json --versions versions.json
   

   Refer to Installing Automation Suite.

3. If Istio is managed externally (not by uipathctl), update the following parameters in the WASM plugin configuration:

   • fqdn - Change the value from the cluster_fqdn to the traffic manager FQDN.
   • uipath_service_namespace - Set this to the same value as the namespace field in input.json.If these parameters are not updated, Orchestrator may display errors such as:
   • URL is invalid
   • Routing error occurs in the WASM plugin: error status returned by host: bad argument