automation-suite
2.2510
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Setting up Kerberos authentication
- Configuring the FQDN post-installation
- Switching to the secondary cluster manually in an Active/Passive setup
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
Automation Suite on OpenShift installation guide
Last updated Nov 13, 2025
You can convert an existing installation into multi-site by taking the following steps:
-
Convert the standalone Automation Suite cluster into the primary cluster. For details, see Converting a standalone cluster into a primary cluster.
-
Install secondary Automation Suite cluster. For details, see Disaster Recovery - Installing the secondary cluster.
Note: Ensure that the certificates are the same on the primary and secondary clusters. This check is not performed or enforced
automatically.
To convert an existing Automation Suite cluster into a primary cluster of the multi-site deployment, take the following steps:
- Update
input.json. Add or updatefqdn,cluster_fqdn, and enablemultisite."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. - Reapply the manifest by running the following command:Refer to Installing Automation Suite.
uipathctl manifest apply input.json --versions version.jsonuipathctl manifest apply input.json --versions version.json
