Configuring your IBM RPA custom resource for high availability

IBM RPA can be configured for high availability (HA) to ensure operational performance in a high-demand settings and provide redundancy in the event of pod failure. This is achieved by scaling the replica pods for a component to two or more in the custom resource (CR).

HA is not configured by default, this means that each component will only have one replica unless explicitly changed in the CR.

Important: To run IBM MQ in a HA, you will need to set highAvailability to true in the systemQueueProvider attribute, for example: 
systemQueueProvider:
    highAvailability: true

To configure HA, you can customize the number of replicas for each component in the CR. By default, each component has only one replica. For a complete high availability configuration, you need more than one replica. Most deployments would not need anymore than two replicas.

Example

The following example shows a custom resource that configured high availability:

apiVersion: rpa.automation.ibm.com/v1beta1
kind: RoboticProcessAutomation
metadata:
  name: rpa-sample
spec:
  license:
    accept: true
  version: 2.3.0
  tls: {}
  api:
    externalConnection:
      secretName: rpa-db
    firstTenant:
      name: ibm
      owner:
        email: superuser@example.com
    replicas: 2
    smtp:
      port: 587
      server: smtp.example.com
      userSecret:
        secretName: rpa-smtp
    storage: {}
  ui:
    replicas: 2
  ocr:
    replicas: 2
  antivirus:
    replicas: 2
  nlp:
    replicas: 2
  systemQueueProvider:
    highAvailability: true