- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Prerequisite checks
- Output example: prerequisite check
- 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: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting

Automation Suite on OpenShift installation guide
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>
namespace. You must either grant the
uipathctl
tool the necessary permissions to allow the creation of
the <uipath>
namespace or create it yourself before running the
checks/tests. Additionally, some checks/tests require that you enable the use of
hostNetwork
.
Ran CONNECTIVITY checks...
⚠ [CONNECTIVITY]
⚠ [NETWORK_TEST_SETUP] Failed to create the network test infrastructure: failed to create echo-host-role role: error creating role: roles.rbac.authorization.k8s.io "network-prereq-6c5mt-echo-host-role" is forbidden: user "system:serviceaccount:uipath:uipathadmin" (groups=["system:serviceaccounts" "system:serviceaccounts:uipath" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:["security.openshift.io"], Resources:["securitycontextconstraints"], ResourceNames:["hostnetwork-v2"], Verbs:["use"]}
Ran CONNECTIVITY checks...
⚠ [CONNECTIVITY]
⚠ [NETWORK_TEST_SETUP] Failed to create the network test infrastructure: failed to create echo-host-role role: error creating role: roles.rbac.authorization.k8s.io "network-prereq-6c5mt-echo-host-role" is forbidden: user "system:serviceaccount:uipath:uipathadmin" (groups=["system:serviceaccounts" "system:serviceaccounts:uipath" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
{APIGroups:["security.openshift.io"], Resources:["securitycontextconstraints"], ResourceNames:["hostnetwork-v2"], Verbs:["use"]}
The checks in the following table are run on each node:
Check |
Description |
---|---|
SQL Connection |
Validates that Automation Suite can successfully connect to the SQL server for UiPath® products
and shared services (such as Identity, Portal, Org Mamagement,
etc.) using the SQL connection strings provided in the
input.json file. 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 objectstore APIs are accessible based on access information provided in the
input.json file. This is mandatory for a
successful installation of the UiPath® services.
|
Cache / Redis |
Validates the connection to Redis. This is mandatory for a successful installation. |
Capacity |
Validates you have minimum CPU and RAM capacity on the worker nodes based on the products enabled
in the
input.json file.
|
Storage Class |
Validates that 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 the 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:
|