Scaling the Db2 Data Gate instance

Important: IBM Cloud Pak® for Data Version 4.8 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.

Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.8 reaches end of support. For more information, see Upgrading from IBM Cloud Pak for Data Version 4.8 to IBM Software Hub Version 5.1.

You can scale the Db2 Data Gate instance from small to large.

Procedure

  1. Before making changes, review the System requirements.
  2. Choose the size of the instance according to this table (e.g., from small to medium, or NIL to large. The default level is CUSTOM. Size is NIL when you provision the instance from the UI.)
    Level Size Description
    level_1 small_mincpureq 2 vCPUs +16 GB Memory
    level_2 small 2 vCPUs +16 GB Memory
    level_3 medium 6 vCPUs +24 GB Memory
    level_4 large 10 vCPUs +32 GB Memory
    level_5 large 10 vCPUs +32 GB Memory
  3. Log in to your Red Hat® OpenShift® cluster as an instance administrator:
    oc login ${OCP_URL}
  4. Change to the project where Db2 Data Gate is installed:
    oc project ${PROJECT_CPD_INST_OPERANDS}
  5. From the command line of the Red Hat OpenShift cluster where Db2 Data Gate is installed, identify the Db2 Data Gate instance identifier by issuing the oc get dginstance command. For example:
    oc get dginstance -n ${PROJECT_CPD_INST_OPERANDS}
    NAME                 VERSION   BUILD      STATUS      RECONCILED   AGE
    dg1699914520773847   5.0.0     5.0.0.82   Completed   5.0.0        6h58m

    In this example, the instance name is dg1699914520773847.

  6. Identify the current scale configuration (the default scale level is CUSTOM).
    cpd-cli manage get-scale-config --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} --components=datagate_instance
  7. Create an override.yaml file to specify the Db2 Data Gate instance need to be scaled. Update according to the results in step 5.
    override_components_meta:
      datagate_instance:
        cr_name: <datagate instance name>
  8. Put the override.yaml file into the workspace of CPD_CLI.
    cp override.yaml ${CPD_CLI_MANAGE_WORKSPACE}/olm-utils-workspace/work
  9. Specify the scale_level according to the table in step 2, and then run the scale command.
    cpd-cli manage apply-scale-config --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS} --components=datagate_instance --scale=<scale_level> --param-file=/tmp/work/override.yaml
  10. Wait for the pod to be ready.
    oc get po -n ${PROJECT_CPD_INST_OPERANDS} | grep <datagate instance name>