- 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
Prerequisite checks
input.json
before starting the Automation Suite installation.
command. By default, this command verifies all the prerequisites. You can use the following flags:
-
--excluded
, if you want to exclude components from the execution. -
--verbose
, if you want to access the detailed prerequisites check output. You can skip this flag for a more concise and simplified output.
uipath-check
namespace. You must either allow the creation of the
uipath-check
namespace or create it yourself before running the
checks/tests. In addition to this, some checks/tests require that you allow the
communication between the uipath-check
and uipath
namespaces, or that you enable the use of hostNetwork
.
The checks in the following table are run on each node:
Check |
Description |
---|---|
SQL Connection |
Validates that Automation Suite can successfully connect to SQL server for UiPath® products and shared services (such as Identity,
Portal, Org Mamagement, etc.) using the SQL connection strings provided in
input.json . This is mandatory for a successful installation.
|
SQL DB roles |
Validates the necessary roles and permissions required by UiPath® products. This is mandatory for a successful installation. |
SQL DB compatibility |
Validates SQL DB compatibility requirements. |
FQDN resolution |
Validates that the FQDN and the sub-domains are successfully resolvable. |
Object Storage API |
Validates that Object store APIs are accessible based on access information provided in
input.json . This is mandatory for a successful installation of UiPath® Services.
|
Cache / Redis |
Validates the connection to Cloud Redis or ElastiCache. This is mandatory for a successful installation. |
Capacity |
Validates you have minimum worker nodes' CPU and RAM capacity based on products enabled in
input.json .
|
Storage Class |
Validates the storage classes for File Storage are configured as required for Automation Suite Robots. |
Optional Components |
Validates that your cluster has components that you chose to exclude from the Automation Suite installation. |
Ingress |
Validates that the cluster ingress is configured correctly and the FQDN URL requests can reach UiPath® products. |
Network Policies |
Checks if network policies configured in Automation Suite are compatible with the cluster. |
Registry |
Validates that Automation Suite can access the UiPath® docker registry. This is mandatory for a successful installation. |
Cluster Connectivity |
Validates whether the cluster communication is configured properly:
|