Deploying Redis through OperatorHub

Install Redis Enterprise Operator through OpenShift OperatorHub for caching in Automation Suite.

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, configure a separate Redis instance for each installation. Do not share a single Redis instance across multiple Automation Suite installations.

Each Redis instance can reside in any namespace in the cluster - it does not have to match the namespace of the Automation Suite installation it serves. However, each Redis instance must use its own dedicated namespace; two Redis instances cannot share a namespace. For each installation, specify that installation's Redis hostname and credentials in its input.json file.

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 details, refer to the Redis documentation.

Installing Redis Enterprise Operator

Take the following steps to install Redis Enterprise Operator through OperatorHub:

1. In the OpenShift interface, navigate to Operators > OperatorHub.
2. In the search field, search for Redis Enterprise.
3. 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.
4. On the Install Operator page, specify the namespace for the operator. Only one namespace per operator is supported.
5. Update the channel with the version you want to install. For details about specific versions, refer to the operator release notes.
6. Choose an approval strategy. For production systems, use Manual to make sure that operator updates require your approval.
7. Select Install and approve the installation plan.

You can monitor the status of your Redis Enterprise Operator subscription in Operators > Installed Operators.

Creating the Redis Enterprise cluster

Take the following steps to create the Redis Enterprise cluster:

1. Create a redis-enterprise-cluster.yaml file with the following contents:

   ---
   apiVersion: app.redislabs.com/v1
   kind: RedisEnterpriseCluster
   metadata:
     name: rec
   spec:
     bootstrapperImageSpec:
       repository: registry.connect.redhat.com/redislabs/redis-enterprise-operator
     persistentSpec:
       enabled: true
     redisEnterpriseServicesRiggerImageSpec:
       repository: registry.connect.redhat.com/redislabs/services-manager
     redisEnterpriseImageSpec:
       imagePullPolicy: IfNotPresent
       repository: registry.connect.redhat.com/redislabs/redis-enterprise
     nodes: 1
     uiServiceType: ClusterIP
   

   Set the value of the nodes parameter in the YAML file to determine the number of pods running in the Redis Enterprise cluster.

2. Apply the configuration in the YAML file to the OpenShift cluster by running the following command:

   Note:

   Replace the <redis-namespace> placeholder in the command with the namespace that you used in the previous step.

   oc apply -f redis-enterprise-cluster.yaml -n "<redis-namespace>"
   

3. Verify that the cluster is in a Running state by using the following command. The command requires the jq utility to be installed on your machine.

   oc get RedisEnterpriseCluster -n <redis-system> -o json | jq -r '.items[0].status.state'
   

   To install jq, use one of the following options:

   • Option 1: Run the following command:

     yum install -y epel-release yum install -y jq
     

   • Option 2: Run the following commands:

     shell
     curl https://download-ib01.fedoraproject.org/pub/epel/7/x86_64/Packages/j/jq-1.6-2.el7.x86_64.rpm --output /tmp/jq-1.6-2.el7.x86_64.rpm
     yum localinstall /tmp/jq-1.6-2.el7.x86_64.rpm
     

Creating the Redis database

Take the following steps to create the Redis database:

1. Create a redis-database.yaml file with the following contents:

   ---
   apiVersion: app.redislabs.com/v1alpha1
   kind: RedisEnterpriseDatabase
   metadata:
     name: redb
   spec:
     tlsMode: disabled
     databasePort: 6380
   

2. Apply the configuration in the YAML file to the OpenShift cluster by running the following command:
   Note:

   Replace the <redis-namespace> placeholder in the command with the namespace that you used in the previous step.

   oc apply -f redis-database.yaml -n "<redis-namespace>"
   

3. Verify that the database is in an active state by running the following command:

   oc get redisenterprisedatabase -n "<redis_namespace>" -o json | jq -r '.items[0].status.status'
   

Updating the cluster configuration file

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
    }
  },

To retrieve the password, run the following command:

oc get secret -n <redis-namespace> redb-redb -o json | jq -r '.data.password' | base64 -d