automation-suite
2023.10
false
Automation Suite on EKS/AKS installation guide
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Saving the connection strings
- Step 2: Creating your organizations in Automation Suite
- 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: Migrating standalone Test Manager
- Step 9: 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
- 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
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Connection strings and tenant names to save before migrating standalone products to Automation Suite.
Save the following information for further usage:
- The connection string for the Orchestrator database in the standalone deployment;
- The
test-automationdatabase connection string.
- The
- The connection string for the Insights database in the standalone deployment;
- The connection string for the
AutomationSuite_Platformdatabase in the Automation Suite deployment. You can retrieve the connection string from theinput.jsonfile, under theplatformparameter. - The following Test Manager information from the
appsettings.production.jsonfile located in the Test Manager installation directory:-
The connection string for the Test Manager database in the standalone deployment.
You can find the connection string in the following key:
Database.ConnectionString.testmanagementhub. -
The storage location information stored in the
Storage.Locationkey. -
The information stored in the
Security.DataEncryptionKeykey.
Note:If the
appsettings.production.jsonfile is encrypted, you can use the Test Manager provisioning tool to decrypt it. For more information, visit Test Manager config file encryption. -