automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
- AI Center provisioning failure after upgrading to 2023.10 or later
- Insights volumes created in two different zones following migration
- Upgrade fails due to overridden Insights PVC sizes
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
Automation Suite on EKS/AKS installation guide
Last updated Oct 13, 2025
When you migrate from Automation Suite on Linux to Automation Suite on EKS/AKS and your target cluster spans multiple zones, Insights-related volumes are occasionally created in two different zones. As a result, you may encounter issues when bringing up the Insights service.
To address the problem, take the following steps:
-
Before migration, cordon the nodes in all zones, with the exception of the zone where you want the volumes to be located. To cordon the nodes, run the following command:
kubectl cordon <node name>kubectl cordon <node name> -
Execute the Automation Suite on Linux to Automation Suite on EKS/AKS migration by running the command in Step 1 of Execution.
-
Uncordon all the nodes you cordoned before the migration by running the following command:
kubectl uncordon <node name>kubectl uncordon <node name>
