automation-suite
2023.4
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration options
- 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 Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
OUT OF SUPPORT
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 21, 2024
AKS upgrades cause Automation Suite to fail
An upgrade known issue affecting AKS causes Automation Suite 2023.4.1-2023.4.5 to fail. When trying to upgrade AKS, the
argocd-redis-ha-server pod is put in error state.
To fix the issue, take the following steps:
-
Uninstall the existing ArgoCD chart by running the following command. Note that the
kubeconfigpath should be set to the cluster path.helm uninstall argocd -n argocdhelm uninstall argocd -n argocd -
Search for the
profilekey in the root level ofinput.json.-
If it is present, change the value of the
profilekey todefault. -
If not present, add the
"profile":"default"key in the root level ofinput.json.
-
-
Reinstall the ArgoCD chart by running the following command:
uipathctl manifest apply input.json --versions versions.json --only argocduipathctl manifest apply input.json --versions versions.json --only argocd
