Setting up an etcd store for HADR

You must set up an etcd store to enable automated failover in a Db2 or Db2 Warehouse High Availability Disaster Recovery (HADR) configuration on Red Hat OpenShift.

Db2 or Db2 Warehouse HADR supports automated failover by using a mechanism called Governor. Governor relies on an etcd key-value store to keep track of HADR state information, such as the current leader (primary node). Automated failover is only supported between the primary and principal standby, so a single etcd endpoint must be shared between the two deployments.

Note: If using the built-in etcd store with the etcd pod, create a network policy to allow communication from all deployments with the etcd pod. For more information, see Creating a network policy for built-in etcd.

The external etcd store can be a cloud provided service, deployed on the OpenShift® cluster, or hosted on-premise.

Important: For production deployments, a three-node etcd topology is required.

If etcd is installed on the same OpenShift cluster, it should not be co-located on the same worker nodes as the Db2 or Db2 Warehouse deployments. This can be achieved using pod anti-affinity in the etcd deployment.

To set up an etcd store for HADR, choose from the following methods:
  • Deploy an external etcd store on an OpenShift® cluster, on a hosted on-premise Db2 instance, or as a cloud-provided service.
  • Deploy the etcd that is packaged with the Db2 or Db2 Warehouse installation.
  • Deploy the etcd that is packaged by Bitnami.
  • Use the built-in etcd store (non-production, single OpenShift cluster environments only).