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
- Installation fails when Velero is enabled
- 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 Dec 4, 2025
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
