Restarting the Informix cluster

This topic explains the procedure to restart pods in the Informix cluster.

About this task

When you install a custom TLS certificate or upgrade your Informix license you will need to restart pods in the Informix cluster to make these changes active. This procedure describes the steps that you need to do to achieve this.

When the certificate is renewed by either certificate rotation or by the injection of a certificate (bring you own certificate - BYOC) then all pods of an Informix cluster need to be restarted. You can achieve this by following the procedure of setting the number of replicas for the custom resources (CRs) Informixes, InformixCMs, Wlisteners and Monitors to 0 and back to the original value - which should be noted down first.

Procedure

  1. Change into the project where your Informix cluster is installed - we will use "zen" in the examples here, you will need to replace "zen" with your project name: 
    oc project zen
  2. List existing Informix CRs in this project: 
    oc get Informixes

    "informix-0123456789012345" with your CR name:

  3. Determine the number of replicas of the Informix CR in question - we are using "informix-0123456789012345" here, you will need to replace "informix-0123456789012345" with your CR name: 
    oc get Informixes informix-0123456789012345 -o template --template 'spec.replicas "\n"'

    and make a note of the returned value.

  4. Patch the Informix CRs to use 0 replicas. 
    oc patch Informixes informix-0123456789012345 --patch '{"spec":{"replicas":0}}' --type=merge
  5. Wait until all Informix pods are terminated.
  6. Patch the Informix CR to use the number of replicas that you noted down in step 3. 
    oc patch Informixes informix-0123456789012345 --patch '{"spec":{"replicas":2}}' --type=merge
  7. Now repeat steps 3. to 6. for the InformixCMs, Wlisteners and Monitors.

    For Monitors we expect only one pod to exist. In case you have more than one running it would now be time to correct it by using "1" as number of replicas in step 6. for the Monitors CR.

    Once all pods are restarted the new certificate will be in place and usable.

    Note: When you replace the Informix edition with a new version you will need to restart only the Informix server pods to make the change active. Therefore you do not have to perform the steps 3. to 6. for the InformixCMs, Wlisteners and Monitors.