- 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
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- 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 EKS/AKS installation guide
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 Automation Suite cluster.
- Bring back all products.
- Run
manifest applywith all products enabled. - If maintenance mode is enabled, disable it using
uipathctl maintenance disable.
- Run
- Wait for all the components and products to be healthy.
- Sync the AI Center skills on the secondary cluster.
- Restore the PVC data for Studio Web and Insights on the secondary cluster.
- For details, refer to EKS backup and restore or AKS backup and restore.
- If you use Velero File System Backup (FSB), you must:
- Before running the restore, uninstall Studio Web and Insights on the secondary cluster. For details, refer to Managing products.
- After the restore completes, reinstall Studio Web and Insights.
Note: This step is required because Velero must re-create the PVCs during restore, and existing PVCs would interfere with that operation. For more details, refer to:
- Switch the traffic to the secondary cluster (update DNS/LB as per your topology)
You can scale up the cluster and bring back all inactive products using the following command:
uipathctl config products scale-upuipathctl config products scale-up To scale down the cluster and switch off inactive products, refer to Switching off inactive products.
You can use the following script to re-sync the AI Center ML Skilll 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]|
Parameter |
Description |
|---|---|
|
|
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-3232uipathctl 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-3232To monitor the skill status, you must run a different script, as shown in the following section.
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]-
InProgess- 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.
