Automation Suite on OpenShift installation guide

Last updated Nov 13, 2025

Disaster recovery - Installing the secondary cluster

To install the secondary Automation Suite cluster in an Active/Passive deployment, take the following steps.

Generate or copy the input.json file from the primary Automation Suite cluster. For more details, see Generating or copying the configuration file of the primary cluster.
Update the input.json file with the parameters specific to the secondary Automation Suite cluster.
Resume the Automation Suite installation.
Switch off inactive products if you use an Active/Passive configuration.

Generating or copying the configuration file of the primary cluster

Generate a new input.json file or copy it from the primary cluster.

uipathctl manifest get-revision --namespace <uipath> >> /path/to/new/input.jsonuipathctl manifest get-revision --namespace <uipath> >> /path/to/new/input.json

Updating the configuration file

Update the input.json file with the parameters specific to the secondary Automation Suite cluster by taking the following steps:

Turn off the unsupported products.
Set all the products that are not supported in multi-site to false.
- For an Active/Passive configuration, disable the products that do not support Active/Passive. For details on Active/Passive support at product level, refer to the table in Disaster recovery - Active/Passive. The following example shows how to disable products:
```
{
  "test_manager": {
    "enabled": false
  },
  "process_mining": {
    "enabled": false
  },
  "automation_hub": {
    "enabled": false
  },
  "insights": {
    "enabled": false
  },
  "autopiloteveryone": {
    "enabled": false
  },
  "automationsolutions": {
    "enabled": false
  } 
}{
  "test_manager": {
    "enabled": false
  },
  "process_mining": {
    "enabled": false
  },
  "automation_hub": {
    "enabled": false
  },
  "insights": {
    "enabled": false
  },
  "autopiloteveryone": {
    "enabled": false
  },
  "automationsolutions": {
    "enabled": false
  } 
}
```
Note:
Make sure that you enable the platform service as shown in the following example:
```
"platform": {
    "enabled": true
  },  "platform": {
    "enabled": true
  },
```

Update the input.json file with the parameters specific to the secondary cluster. You must provide the kubeconfig of the primary cluster, as it is required for the secondary cluster to access the configurations made on the primary cluster.

"fqdn" : "<global traffic manager fqdn>"
"cluster_fqdn": "<fqdn of the secondary cluster>",

"multisite": {
    "enabled": true,
    "primary": false,
    "other_kube_config": "[base64 encoded kubeconfig]"
 }"fqdn" : "<global traffic manager fqdn>"
"cluster_fqdn": "<fqdn of the secondary cluster>",

"multisite": {
    "enabled": true,
    "primary": false,
    "other_kube_config": "[base64 encoded kubeconfig]"
 }

For details, see Advanced installation experience.

You must keep the namespace in the secondary cluster the same as in the primary cluster because, during the secondary installation, several configurations are copied from the primary cluster.
```
"namespace": "<namespace same as primary>""namespace": "<namespace same as primary>"
```

You must ensure that the namespaces for ArgoCD and Istio are set correctly.

"ingress": {
  "namespace": "<namespace where istio is installed>",
}
"argocd": {
  "application_namespace": "<namespace where istio is installed>"
}"ingress": {
  "namespace": "<namespace where istio is installed>",
}
"argocd": {
  "application_namespace": "<namespace where istio is installed>"
}

Resume the installation

Once the parameters in the previous step are provided or modified in the input.json, you can resume the installation. For details, refer to Installing Automation Suite.

Note:

You must perform the Automation Suite installation using the uipathctl installer. Note that you do not need to generate a new input.json.

Switching off inactive products

If you deployed Automation Suite in Active/Passive mode, you can scale down the cluster and switch off inactive products using the following command.

uipathctl config products scale-downuipathctl config products scale-down

To scale up the cluster and bring back inactive products, refer to Bringing back the products.

On this page

Generating or copying the configuration file of the primary cluster
Updating the configuration file
Resume the installation
Switching off inactive products

Was this page helpful?

PREVIOUSOutput example: Automation Suite installation

NEXTAccessing Automation Suite

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy