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
- B) 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
Automation Suite on EKS/AKS Installation Guide
Last updated Dec 18, 2024
General troubleshooting
If you encounter general issues while configuring or using Automation Suite, refer to the following:
To address the issue, you must manually modify the Velero deployment:
-
Download the Velero chart from the registry and move it into the appropriate directory, by using the following command:
helm pull oci://<registry_url>/vendor/velero --version 6.2.0 -d . --untarhelm pull oci://<registry_url>/vendor/velero --version 6.2.0 -d . --untar -
Manually override the
credentials.useSecretfield in the Velero configuration, by using the following command:helm upgrade velero ./velero -n velero --set credentials.useSecret=false --reuse-valueshelm upgrade velero ./velero -n velero --set credentials.useSecret=false --reuse-values
