- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- 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
- 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
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Switching to the secondary cluster manually in an Active/Passive setup
Manually switch traffic to secondary cluster during failover in Active/Passive Automation Suite setup.
This section provides high-level instructions on how to manually switch the traffic to the secondary cluster in an Active/Passive setup.
To switch to the secondary Automation Suite cluster, take the following steps:
- Turn on all the nodes of the secondary Automation Suite cluster.
- Bring back all previously active products.
- Wait for all components and products to reach a healthy operational state.
- Sync the AI Center skills on the secondary cluster.
- Switch the traffic to the secondary cluster (update DNS/LB as per your topology)
When switching to the secondary site, products such as Insights, Process Mining, Studio Web, and Automation Hub are not available.
Bringing back the products
To bring back all inactive products, run the following command:
uipathctl cluster maintenance disable
uipathctl cluster maintenance disable
Syncing the AI Center ML Skill
You can use the following script to re-sync the AI Center ML Skill in the secondary cluster. The script triggers the re-sync in the background if no active sync is in progress. You can use the same script to switch back to the primary cluster.
The script syncs the skills in the background (async) and returns. The job ensures that the skills are deployed and updates the DB entry to reflect the current status.
uipathctl service aicenter sync-skills [skill_ids]
uipathctl service aicenter sync-skills [skill_ids]
[skill_ids]: The optional array of the skill IDs separated by space. If you provide the skill ID, then only those skills are updated; otherwise, all deployed skills are re-synced.
Example:
uipathctl service aicenter sync-skills 783273-3232-3232-323 32-32-323-3232
//this will only sync the skills with ID 783273-3232-3232-323 and 32-32-323-3232
uipathctl service aicenter sync-skills 783273-3232-3232-323 32-32-323-3232
//this will only sync the skills with ID 783273-3232-3232-323 and 32-32-323-3232
To monitor the skill status, you must run a different script, as shown in the following section.
Checking the status of the AI Center ML Skill
To view the status of the AI Center ML Skill, run the following command:
uipathctl service aicenter sync-skill-status [skill_ids]
uipathctl service aicenter sync-skill-status [skill_ids]
The command can return any of the following statuses:
InProgress- skill deployment is in progress.Failed- skill deployment is failed.OutOfSync- skill is available in the database; however, it has yet to be deployed.Available- when the skills are deployed and available to consume.