automation-suite
2.2510
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting

Automation Suite on OpenShift installation guide
Last updated Nov 13, 2025
UiPath® products on Automation Suite require Redis to ensure caching capabilities. You have the following options for meeting
the Redis caching requirements:
-
Install and configure Redis, either on your OpenShift cluster or on different servers external to the OpenShift cluster.
-
Install the Redis Enterprise Operator on your OpenShift cluster. To install Redis Enterprise Operator through OperatorHub, follow the instructions in this section. If you install multiple Automation Suite instances on the same cluster, make sure to install Redis in all the corresponding namespaces and replace the redis host accordingly in the
input.jsonfile based on each installation.Note:- Automation Suite does not come with a Redis Enterprise Operator license. You must obtain a license directly from Redis or use a UiPath-provided HAA Redis license.
- If you use Redis Enterprise Operator version 6.2.18-41 or earlier, you must install the security context constraint before installing the operator. For more information, see the Redis documentation.
Take the following steps to install Redis Enterprise Operator through OperatorHub:
- In the OpenShift interface, navigate to Operators > OperatorHub.
- In the search field, search for Redis Enterprise.
- Select Redis Enterprise Operator provided by Redis in the result list. The entry is marked as Certified. By default, the image is pulled from the Red Had registry.
- On the Install Operator page, specify the namespace for the operator. Only one namespace per operator is supported.
- Update the channel with the version you want to install. For more information about specific versions, see the operator release notes.
- Choose an approval strategy. For production systems, use Manual to make sure that operator updates require your approval.
- Select Install and approve the installation plan.
You can monitor the status of your Redis Enterprise Operator subscription in Operators > Installed Operators.
Take the following steps to create the Redis Enterprise cluster:
Deploying Redis through OperatorHub requires you to add the following section to the
input.json configuration file. Replace the <redis-namespace> and <password> placeholders with appropriate values:"fabric": {
"redis": {
"hostname": "redb.<redis-namespace>.svc.cluster.local",
"port": 6380,
"password": "<password>",
"tls": false
}
}, "fabric": {
"redis": {
"hostname": "redb.<redis-namespace>.svc.cluster.local",
"port": 6380,
"password": "<password>",
"tls": false
}
},To retrieve the password, run the following command:
oc get secret -n <redis-namespace> redb-redb -o json | jq -r '.data.password' | base64 -doc get secret -n <redis-namespace> redb-redb -o json | jq -r '.data.password' | base64 -d