automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- 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 creation
- Troubleshooting
- Installation fails when Velero is enabled
- Issue with connecting to the Multi-AZ database server
- 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
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error

Automation Suite on EKS/AKS installation guide
Last updated Mar 31, 2026
Installation fails when Velero is enabled
Description
The Automation Suite installation might fail when Velero is enabled.
Solution
To fix the issue, take the following steps:
-
Make sure Helm 3.14 runs on the jumpbox or laptop used for installing Automation Suite.
-
Extract the configuration values of the failed Helm chart, which in this case is Velero:
helm -n velero get values velero > customvals.yamlhelm -n velero get values velero > customvals.yaml -
Add the missing image pull secret in the
customvals.yamlfile, under the.image.imagePullSecretspath:image: imagePullSecrets: - uipathpullsecretimage: imagePullSecrets: - uipathpullsecret -
If Velero has already been installed, uninstall it:
helm uninstall -n velero velerohelm uninstall -n velero velero -
Create a new file called
velerosecrets.txt. Populate it with your specific information, as shown in the following example:AZURE_CLIENT_SECRET=<secretforserviceprincipal> AZURE_CLIENT_ID=<clientidforserviceprincipal> AZURE_TENANT_ID=<tenantidforserviceprincipal> AZURE_SUBSCRIPTION_ID=<subscriptionidforserviceprincipal> AZURE_CLOUD_NAME=AzurePublicCloud AZURE_RESOURCE_GROUP=<infraresourcegroupoftheakscluster>AZURE_CLIENT_SECRET=<secretforserviceprincipal> AZURE_CLIENT_ID=<clientidforserviceprincipal> AZURE_TENANT_ID=<tenantidforserviceprincipal> AZURE_SUBSCRIPTION_ID=<subscriptionidforserviceprincipal> AZURE_CLOUD_NAME=AzurePublicCloud AZURE_RESOURCE_GROUP=<infraresourcegroupoftheakscluster> -
Encode the
velerosecrets.txtfile:export b64velerodata=$(cat velerosecrets.txt | base64)export b64velerodata=$(cat velerosecrets.txt | base64) -
Create the
velero-azuresecret in theveleronamespace. Include the following content:apiVersion: v1 kind: Secret metadata: name: velero-azure namespace: velero data: cloud: <put the $b64velerodata value here>apiVersion: v1 kind: Secret metadata: name: velero-azure namespace: velero data: cloud: <put the $b64velerodata value here> -
Reinstall Velero:
helm install velero -n velero <path to velero - 3.1.6 helm chart tgz> -f customvals.yamlhelm install velero -n velero <path to velero - 3.1.6 helm chart tgz> -f customvals.yaml