Storage requirements

IBM RPA on Red Hat® OpenShift® Container Platform has two mandatory persistent volumes: Archive and Hot. IBM Automation Foundation Core and IBM MQ are installed as prerequisites by the IBM RPA operator. They also create their own persistent volumes.

The IBM RPA operator creates persistent volume claims for the volumes by default, but it is possible to customize them in two ways:

  1. Supply your own persistent volume claims.
    You can pre-create your own persistent volume claims for the archive and hot volumes. Their names must match the names that are used by the operator, which is shown in the Persistent volumes details table. The storage class that you use must support the ReadWriteMany (rwx) access mode.

  2. Configure persistent volume claim properties in the IBM RPA custom resource.
    You can set properties such as the storage class, size, and permissions for each volume in the IBM RPA CR. For more information, see the following sections.

Persistent volumes to satisfy the persistent volume claims can either be dynamically provisioned, or pre-created.

When you delete an IBM RPA custom resource, the persistent volume claims are not removed. You can manually delete them when data stored there is no longer required. If you create a new IBM RPA custom resource with the same name as a previous one, the existing persistent volume claims are reused. Any existing data on the volumes is used for the new IBM RPA instance.

Note:The data on the persistent volumes must be backed up manually.

Persistent volumes details

Used by Default name Dynamically created Default size (GB) Mandatory Access Modes
Archive storage <instance-name>-apiserver-rpa-archive Yes 1 GB Yes ReadWriteMany
Hot storage <instance-name>-apiserver-rpa-hot Yes 10 GB Yes ReadWriteMany