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: 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)
You can modify various Orchestrator parameters using uipathctl. This enables the following configuration scenarios:
- Overriding cluster-level storage configuration
- Saving robot logs to Elasticsearch
- Configuring encryption key per tenant
To do that, edit the input.json file, add or edit the settings under the orchestrator section, then run the following command:
./uipathctl manifest apply input.json --versions versions.json --kubeconfig kubeconfig.yaml --only orchestrator
./uipathctl manifest apply input.json --versions versions.json --kubeconfig kubeconfig.yaml --only orchestrator
For details on input.json, refer to Configuring input.json.
For details, on the Orchestrator-specific configuration, refer to Orchestrator configuration.