- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- 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
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Caching
Configure Redis for distributed caching in Automation Suite on OpenShift.
UiPath® products on Automation Suite require Redis to ensure caching capabilities. For a list of prerequisites and compatible Redis versions, refer to Compatibility matrix.
Multiple services in Automation Suite, such as Orchestrator and Identity, use Redis as a distributed cache, for speeding up critical and high volume operations. These services store data that is accessed frequently in Redis, to avoid either retrieving the data from the database or doing expensive computations multiple times.
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 OpenShift Redis Enterprise Operator on your OpenShift cluster in one of the following ways:
- Perform the installation via OpenShift Operator Hub. For installation instructions, refer to Deploy Redis Enterprise with OpenShift OperatorHub.
- Perform the installation via CLI. For installation instructions, refer to Deployment with OpenShift CLI for Redis Enterprise for Kubernetes.
Note:UiPath® support does not cover OpenShift Redis Enterprise Operator. You must address OpenShift Redis Enterprise Operator support requests directly to Red Hat or Redis Enterprise.
You can activate the OpenShift Redis Enterprise Operator from OperatorHub using a UiPath-provided HAA Redis license or a Redis license obtained directly from Redis.
If you configure Redis Enterprise without applying a valid production license, the Redis trial license may expire after 30 days. This can lead to licensing-related restrictions and operational risk.
After meeting the caching prerequisites, you must pass the access information in the input.json file, as shown in the following example:
"fabric": {
"redis": {
"hostname": "xx",
"password": "xx",
"port": 6380,
"tls": true
}
}
"fabric": {
"redis": {
"hostname": "xx",
"password": "xx",
"port": 6380,
"tls": true
}
}
Set the value of the tls parameter to true only if the Redis URL is trusted by a known authority or if you added the certificates to the additional CA certificates. Otherwise, set the value of the tls parameter to false.