Configuring high availability for foundational services

Configure high availability (HA) for IBM Cloud Pak foundational services.

Install more than one instance of foundational services for HA. You can configure HA for all or some services that you are installing in your cluster.

Prerequisites

Before you configure HA, see the Hardware requirements and recommendations for foundational services.

Configure HA

See the following sections for the HA configuration of each service.

• IAM
• Management ingress
• Platform API
• User Data Services

IAM

Update the ibm-iam-operator spec in the OperandConfig before or after you install foundational services.

For more information, see HA configuration.

Management ingress

You can configure HA for the management ingress only after you deployed an instance of the management ingress service.

First, install the ibm-management-ingress-operator when you install IBM Cloud Pak foundational services. For more information, see Installing IBM Cloud Pak foundational services by using the OpenShift console.

1. Verify the status of the management-ingress deployment.

   oc get deployment management-ingress -n ibm-common-services
   

   Following is a sample output:

   NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
   management-ingress   1/1     1            1           4d20h
   

2. Edit the management-ingress deployment.

   oc edit deployment management-ingress -n ibm-common-services
   

   Following is a sample output:

   # Please edit the following object. Lines beginning with a '#' will be ignored,
   # and an empty file will abort the edit. If an error occurs while saving this file will be
   # reopened with the relevant failures.
   #
   apiVersion: extensions/v1beta1
   kind: Deployment
   metadata:
    annotations:
      deployment.kubernetes.io/revision: "1"
   .
   .
   labels:
      app: management-ingress
      app.kubernetes.io/component: management-ingress
   .
   .
   spec:
    progressDeadlineSeconds: 600
    replicas: 1
    revisionHistoryLimit: 10
    selector:
      matchLabels:
   .
   .
   

3. Change the spec.replicas parameter value from 1 to the number of replicas that you want.

4. Save the changes. You see the following message:

   deployment.extensions/management-ingress edited
   

5. Check the rollout status.

   oc rollout status deployment.extensions/management-ingress
   

   Here is a sample status:

   deployment "management-ingress" successfully rolled out
   

6. Verify the status of the management-ingress deployment.

   oc get deployment management-ingress -n ibm-common-services
   

   Following is a sample output:

   NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
   management-ingress   2/2     2            2           4d20h
   

Platform API

To enable HA for Platform API, increase the replicaCount parameter value to the number of replicas that you want. For more information, see Platform API settings.

User Data Services

To enable HA for User Data Services, set the env_type parameter value to prod. For more information, see the User Data Services documentation.