Configuring Native HA using the IBM MQ Operator

Native HA is configured using the QueueManager API, and advanced options are available using an INI file.

Native HA is configured using the .spec.queueManager.availability of the QueueManager API

Note: The following YAML uses an IBM® MQ Advanced license. IBM MQ licensed queue managers can also be configured to use Native HA and Cross-Region Replication features by adding additional licenses to a queue manager. For more information, see Configuring Native HA and Cross-Region Replication on IBM MQ licensed Queue Managers by using the IBM MQ Operator.

Example QueueManager for Red Hat® OpenShift®

apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata:
  name: nativeha-example
spec:
  license:
    accept: false
    license: L-CXDB-XTZ9J8
    use: Production
  queueManager:
    availability:
      type: NativeHA
  version: 10.0.0.0-r1

Example QueueManager for Amazon EKS

apiVersion: mq.ibm.com/v1beta1
kind: QueueManager
metadata:
  name: nativeha-example
spec:
  license:
    accept: false
    license: L-CXDB-XTZ9J8
    use: Production
  queueManager:
    availability:
      type: NativeHA
    route:
      enabled: false
    metrics:
      serviceMonitor:
        enabled: false
  version: 10.0.0.0-r1
  web:
    enabled: false
    route:
      enabled: false

spec.queueManager.route.enabled, spec.queueManager.metrics.serviceMonitor.enabled, and spec.web.route.enabled are set to false because they are Red Hat OpenShift specific features that are enabled by default. These features must be disabled explicitly on Amazon EKS.

The .spec.queueManager.availability.type field must be set to NativeHA.

Under .spec.queueManager.availability, you can also configure a TLS secret and ciphers to use between queue manager instances when replicating. This is strongly recommended, and a step-by-step guide is available in Example: Configuring Native HA using the IBM MQ Operator.