Changing your deployment to use dedicated resources

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.

After provisioning, you can set your deployment to use dedicated nodes.

Before you begin

You must complete the following tasks:
  1. Configure dedicated nodes to use for your deployment. For more information, see Setting up dedicated nodes for your Db2 deployment.
  2. Create a Db2 deployment and ensure it is in Ready state. For more information, see Creating a Db2 database deployment on the cluster.

Procedure

  1. Run the following command to patch your db2ucluster: 
    oc patch db2ucluster <instance_id> -n ${PROJECT_CPD_INST_OPERANDS} --type merge -p '{"spec":{"affinity":{"nodeAffinity":{"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"icp4data","operator":"In","values":["<label_name>"]}]}]}}},"tolerations":[{"effect":"NoSchedule","key":"icp4data","operator":"Equal","value":"<dedicated_specifier>"}]}}'
  2. Run the following commands to verify that the deployment is now using dedicated nodes: 
    oc get sts c-<instance_id>-db2u -n ${PROJECT_CPD_INST_OPERANDS} -oyaml | grep <dedicated_specifier>
    oc get sts c-<instance_id>-etcd -n ${PROJECT_CPD_INST_OPERANDS} -oyaml | grep <dedicated_specifier>
    Refer to the following example output:
    value: <dedicated_specifier>
    Where <dedicated_specifier> is the assigned label of the node dedicated to the deployment.