- 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 in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Disaster recovery - Installing the secondary cluster
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Disaster recovery - Installing the secondary cluster
Install secondary cluster in multi-site Active/Passive deployment on EKS/AKS.
Active/Passive mode is currently available only for EKS.
To install the secondary Automation Suite cluster in an Active/Passive deployment, take the following steps.
- Generate or copy the
input.jsonfile from the primary Automation Suite cluster. For details, refer to Generating or copying the configuration file of the primary cluster. - Update the
input.jsonfile 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 >> /path/to/new/input.json
uipathctl manifest get-revision >> /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.
Note:Make sure that you enable the
platformservice as shown in the following example:"platform": { "enabled": true },"platform": { "enabled": true }, -
Update the
input.jsonfile 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, refer to Advanced installation experience.
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.
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
This step is required. Skipping it may cause some services to fail.
If you deployed Automation Suite in Active/Passive mode, switch off the inactive products using the following command.
uipathctl cluster maintenance enable
uipathctl cluster maintenance enable