IBM Support

IBM Knowledge Catalog 5.3.0 and IBM watsonx.data intelligence 2.3.0 patch

Fix Readme


Abstract

After you install or upgrade IBM Knowledge Catalog or IBM watsonx.data intelligence on IBM Software Hub Version 5.3.0, apply the patch for the Text-to-SQL feature, SQL search in document libraries, metadata import, and data masking flows.

Content

If you use or plan to use these capabilities in IBM Knowledge Catalog 5.3.0 or IBM watsonx.data intelligence 2.3.0, apply the patch after you install or upgrade the service:

  • Text-to-SQL capabilities

  • Metadata import

  • Data masking flows

  • SAP BW Extract connector 
     
  • DataStage connectors 
     
  • IBM watsonx.data Presto Connector
     
  • Snowflake Connector
     

The patch addresses the following known issues:

 

 

Procedure

This patch tool updates the following components: IKC, IKC standard/premium, Manta Data Lineage, and Data Privacy.

 

Applying the patch

Apply the patch based on your environment:

  1. If you are downloading and copying the images to a local registry for an air-gapped environment, see Apply the hotfix to an air-gapped environment. 

  2. If you are applying the patch using the IBM entitled online registry, or you are applying the hotfix using the images downloaded to a local registry, see Applying the hotfix online or using downloaded images.

 


Apply the hotfix to an air-gapped environment

To apply the patch in an air-gapped environment:

  1. Log in to the OpenShift console as the cluster admin.

  2. Prepare the authentication credentials to access the IBM production repository. Use the same auth.json file used for the CASE download and image mirroring. The following is an example directory path:

    ${HOME}/.airgap/auth.json

    Or create an auth.json file that contains credentials to access icr.io and your local private registry. For example:

    { "auths": { "cp.icr.io":{"email":"unused","auth":"<base64 encoded id:apikey>"}, "<private registry hostname>":{"email":"unused","auth":"<base64 encoded id:password>"} } }

    For more information about the auth.json file, see containers-auth.json - syntax for the registry authentication file.

  3. Install skopeo by running:

    yum install skopeo

  4. To confirm the path for the local private registry to copy the hotfix images to, run the following command:

    oc describe pod <hotfix image pod> | grep -i "image:"

    Where <hotfix image pod> can be the pod name for any of the images which will be patched with this hotfix. For example:

    oc describe pod wdp-connect-connector-9cb5f8c5d-sqb6m -n wkc | grep -i "Image:" … Image: cp.icr.io/cp/cpd/wdp-connect-connector@sha256:289c935ae5ae1b80663e50c55aa76f58cbb47099df78bd58ed2ff442999bcc5c

  5. To get the local private registry source details, run the following commands:

    oc get imageContentSourcePolicy oc describe imageContentSourcePolicy [cloud-pak-for-data-mirror]

    The local private registry mirror repository and path details should be in the output of the describe command:

    mirrors: ${PRIVATE_REGISTRY_LOCATION}/cp/ source: cp.icr.io/cp/cpd

    For more information about mirroring of images, see Configuring your cluster to pull Cloud Pak for Data images.

  6. Use the skopeo command to copy the patch images from the IBM production registry to the local private registry. Using the appropriate auth.json file, copy the patch images from the IBM production registry to the Openshift cluster registry: 

    CCS (amd64 images for x86 installations only)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connection@sha256:ba848283466f8f662cfdcd21047e3c6f4e103e5b70604614e92e6ff9bd2a17d7 \
    docker://<local registry>/cp/cpd/wdp-connect-connection@sha256:ba848283466f8f662cfdcd21047e3c6f4e103e5b70604614e92e6ff9bd2a17d7
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connector@sha256:b36e7298a46baa790ad294c33804b09d9404a2859b4960751dfc3438764d4a29 \
    docker://<local registry>/cp/cpd/wdp-connect-connector@sha256:b36e7298a46baa790ad294c33804b09d9404a2859b4960751dfc3438764d4a29 
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-flight-svc@sha256:d24360c12eeca2a92a0ed66765d08dcfed78c63aeff4191298368a0851cfd144 \
    docker://<local registry>/cp/cpd/wdp-connect-flight-svc@sha256:d24360c12eeca2a92a0ed66765d08dcfed78c63aeff4191298368a0851cfd144


    CCS (ppc64le images for Power installations only)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connection@sha256:ed299ab67cc7829ef48b518e8c8c88520af3091e80cd81f029f6fcfee6fb3e3a \
    docker://<local registry>/cp/cpd/wdp-connect-connection@sha256:ed299ab67cc7829ef48b518e8c8c88520af3091e80cd81f029f6fcfee6fb3e3a
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connector@sha256:92aaa0fb076ef9f348257b28b8be12b1eb2d39c184ecbb3f283a48cbf6564d02 \
    docker://<local registry>/cp/cpd/wdp-connect-connector@sha256:92aaa0fb076ef9f348257b28b8be12b1eb2d39c184ecbb3f283a48cbf6564d02
skopeo copy --all --authfile "<folder path>/auth.json" \ 
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-flight-svc@sha256:0189eba87f84ba38ff6e55c9b3de27cc97bfa74a0adc7cfc7113a93a4b7b1f51 \
    docker://<local registry>/cp/cpd/wdp-connect-flight-svc@sha256:0189eba87f84ba38ff6e55c9b3de27cc97bfa74a0adc7cfc7113a93a4b7b1f51


    CCS (s390x images for IBM System/390 installations only)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connection@sha256:f5b9dd6486e221c2178d08cfe6238fc860f1e1207a56efa1014bbba38976cc1e \
    docker://<local registry>/cp/cpd/wdp-connect-connection@sha256:f5b9dd6486e221c2178d08cfe6238fc860f1e1207a56efa1014bbba38976cc1e
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-connector@sha256:5c216c72b7b020eb471fab2066802e256b65830f654ead8bdaa841a141240108 \
    docker://<local registry>/cp/cpd/wdp-connect-connector@sha256:5c216c72b7b020eb471fab2066802e256b65830f654ead8bdaa841a141240108 
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wdp-connect-flight-svc@sha256:383d2850d36214033b2a0b58f2c1e48d98c8a35a8d1a232727a70d949588f701 \
    docker://<local registry>/cp/cpd/wdp-connect-flight-svc@sha256:383d2850d36214033b2a0b58f2c1e48d98c8a35a8d1a232727a70d949588f701


    IKC (amd64 images for x86 installations only)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://icr.io/cpopen/ibm-cpd-wkc-operator@sha256:7b601d78a630904909d310ba46d5bdf64930e059197483f58a7ad68c7292dc4e \
    docker://<local registry>/cp/ibm-cpd-wkc-operator@sha256:7b601d78a630904909d310ba46d5bdf64930e059197483f58a7ad68c7292dc4e
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/metadata-discovery@sha256:9c7c4a796b80fd60ecdbd0df3a0e8879f4c4d7464dcf97730d1ccf8efe335d31 \
    docker://<local registry>/cp/cpd/metadata-discovery@sha256:9c7c4a796b80fd60ecdbd0df3a0e8879f4c4d7464dcf97730d1ccf8efe335d31
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-data-quality-ui@sha256:dfc0e6b6bb61e316b0ad229707979e79b5b985a1f49d0e1588ac35992518ee11 \
    docker://<local registry>/cp/cpd/wkc-data-quality-ui@sha256:dfc0e6b6bb61e316b0ad229707979e79b5b985a1f49d0e1588ac35992518ee11
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-metadata-imports-ui@sha256:72207909a6cbfe0893f4fef663ac7d5185255cb580368f3d991557e8740a5edf \
    docker://<local registry>/cp/cpd/wkc-metadata-imports-ui@sha256:72207909a6cbfe0893f4fef663ac7d5185255cb580368f3d991557e8740a5edf
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-workflow-service@sha256:6c74c275aafb12a2d93b05ede1966b0b233c6f0fa4fa783cc8f48221008fc04c \
    docker://<local registry>/cp/cpd/wkc-workflow-service@sha256:6c74c275aafb12a2d93b05ede1966b0b233c6f0fa4fa783cc8f48221008fc04c


    IKC (ppc64 images for Power installations only)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://icr.io/cpopen/ibm-cpd-wkc-operator@sha256:6430ccf5419791bcac8c5738c821068cf1c63e4ca9171bf7d14fd21a2f1749ea \
    docker://<local registry>/cp/ibm-cpd-wkc-operator@sha256:6430ccf5419791bcac8c5738c821068cf1c63e4ca9171bf7d14fd21a2f1749ea
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/metadata-discovery@sha256:f123168b26e0cbb90556df36d41ad88ed413479ae32054e47ba02df2944ec508 \
    docker://<local registry>/cp/cpd/metadata-discovery@sha256:f123168b26e0cbb90556df36d41ad88ed413479ae32054e47ba02df2944ec508
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-data-quality-ui@sha256:c4aa17ce4e7446d479bb3b9213d458f925919b360fc9dc00b0f8cbb181a606e7 \
    docker://<local registry>/cp/cpd/wkc-data-quality-ui@sha256:c4aa17ce4e7446d479bb3b9213d458f925919b360fc9dc00b0f8cbb181a606e7
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-metadata-imports-ui@sha256:49c6f1f6de877a47d5ce592f5febce85814daf7abb7229c7b5c39060b23dfe24 \
    docker://<local registry>/cp/cpd/wkc-metadata-imports-ui@sha256:49c6f1f6de877a47d5ce592f5febce85814daf7abb7229c7b5c39060b23dfe24
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/wkc-workflow-service@sha256:dc7f3ac5a087b57f62231a6fbee372915fe588035837b951e1d162c3c76559df \
    docker://<local registry>/cp/cpd/wkc-workflow-service@sha256:dc7f3ac5a087b57f62231a6fbee372915fe588035837b951e1d162c3c76559df


    Semantic Automation (if IKC Standard or IKC Premium is installed)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/semantic-automation-service@sha256:ce919c28aed1fd8a8a7768daf73633f82bb4f526605c6e7aa752cb85e99a7efb \
    docker://<local registry>/cp/cpd/semantic-automation-service@sha256:ce919c28aed1fd8a8a7768daf73633f82bb4f526605c6e7aa752cb85e99a7efb
    
skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/semantic-inference-service@sha256:da3f753a6b3f6644821c9a1684b87fe6be5b4d331c30ca866d8640a4ee83516e \
    docker://<local registry>/cp/cpd/semantic-inference-service@sha256:da3f753a6b3f6644821c9a1684b87fe6be5b4d331c30ca866d8640a4ee83516e


    Data Privacy (if installed)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/dp-ui@sha256:d54d00d45fea9860a1fa523cc61ef026117bf943a5d8f9b8930afdd72fa68275 \
    docker://<local registry>/cp/cpd/dp-ui@sha256:d54d00d45fea9860a1fa523cc61ef026117bf943a5d8f9b8930afdd72fa68275


    Manta Data Lineage (if installed)

    skopeo copy --all --authfile "<folder path>/auth.json" \
    --dest-tls-verify=false --src-tls-verify=false \
    docker://cp.icr.io/cp/cpd/lineage-scanner-service@sha256:93451ab8c54d48caab31081513a293e2240e76052a47dbf01a407f6902051f7e \
    docker://<local registry>/cp/cpd/lineage-scanner-service@sha256:93451ab8c54d48caab31081513a293e2240e76052a47dbf01a407f6902051f7e

 


Apply the hotfix online or using downloaded images

To install the patch using the online IBM entitled registry or to apply the hotfix using the images downloaded to the local registry:

  1. Replace ${PROJECT_CPD_INST_OPERANDS} with the project name where the products are installed (ibm-common-services or cpd-operators for example):

    export PROJECT_CPD_INST_OPERANDS=<enter your Cloud Pak for Data instances project>

 

For CCS

  1. Save a copy of the Common Core Services CR currently deployed on the cluster:

    oc get ccs ccs-cr -o yaml -n ${PROJECT_CPD_INST_OPERANDS} > ccs_cr_backup_<date>.yaml

    Where <date> is the date you are applying the patch.

  2. Run the following command to apply the patch to Common Core Services CR custom resource (ccs-cr):

    For x86 installations

    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"image_digests":{
    "wdp_connect_connection_image": "sha256:ba848283466f8f662cfdcd21047e3c6f4e103e5b70604614e92e6ff9bd2a17d7",
    "wdp_connect_connector_image": "sha256:b36e7298a46baa790ad294c33804b09d9404a2859b4960751dfc3438764d4a29",
    "wdp_connect_flight_image": "sha256:d24360c12eeca2a92a0ed66765d08dcfed78c63aeff4191298368a0851cfd144"
}}}'

    For Power installations

    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"image_digests":{
    "wdp_connect_connection_image": "sha256:ed299ab67cc7829ef48b518e8c8c88520af3091e80cd81f029f6fcfee6fb3e3a",
    "wdp_connect_connector_image": "sha256:92aaa0fb076ef9f348257b28b8be12b1eb2d39c184ecbb3f283a48cbf6564d02",
    "wdp_connect_flight_image": "sha256:0189eba87f84ba38ff6e55c9b3de27cc97bfa74a0adc7cfc7113a93a4b7b1f51"
}}}'

    For s390x installations

    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"image_digests":{
    "wdp_connect_connection_image": "sha256:f5b9dd6486e221c2178d08cfe6238fc860f1e1207a56efa1014bbba38976cc1e",
    "wdp_connect_connector_image": "sha256:5c216c72b7b020eb471fab2066802e256b65830f654ead8bdaa841a141240108",
    "wdp_connect_flight_image": "sha256:383d2850d36214033b2a0b58f2c1e48d98c8a35a8d1a232727a70d949588f701"
}}}'

  3. Wait for the CCS operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the updated images.


For IKC, IKC Standard/Premium, or watsonx.data intelligence

  1. View the helm chart update history and there should be a new revision from the previous upgrade command:

    helm history -n ${PROJECT_CPD_INST_OPERANDS} wkc

    NOTE: Keep track of the previous revision number in case the hotfix needs to be reverted.

  2. Copy the Version 5.3.0 helm chart (ibm-wkc-5.3.0+20251203.234930.305.tgz) to a local location and run the following commands to apply the IKC operator hotfix image override to the IKC helm chart:

    oc label wkc wkc-cr -n ${PROJECT_CPD_INST_OPERANDS} app.kubernetes.io/managed-by=Helm component-id=wkc icpdsupport/addOnId=wkc  
oc annotate wkc wkc-cr -n ${PROJECT_CPD_INST_OPERANDS}  meta.helm.sh/release-name=wkc meta.helm.sh/release-namespace=${PROJECT_CPD_INST_OPERANDS}

     

    For x86 installations

    helm upgrade wkc wkc-5.3.0+20251203.234930.305.tgz --reuse-values --set wkc.operatorImageDigest.amd64=sha256:7b601d78a630904909d310ba46d5bdf64930e059197483f58a7ad68c7292dc4e

    For Power installations

    helm upgrade wkc wkc-5.3.0+20251203.234930.305.tgz --reuse-values --set wkc.operatorImageDigest.ppc64le=sha256:6430ccf5419791bcac8c5738c821068cf1c63e4ca9171bf7d14fd21a2f1749ea

    The helm chart may be downloaded from here or copied from the local cpd-cli workspace directory.

  3. View the helm chart update history and there should be a new revision from the previous upgrade command:

    helm history -n ${PROJECT_CPD_INST_OPERANDS} wkc

    NOTE: Keep track of the previous revision number in case the hotfix needs to be reverted.

  4. Wait for the WKC operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get wkc wkc-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the updated images.

 

For Semantic Automation (if IKC Standard or IKC Premium is installed)

  1. Save a copy of the Semantic Automation custom resource (CR) currently deployed on the cluster:

    oc get semanticautomation semanticautomation-cr -o yaml -n ${PROJECT_CPD_INST_OPERANDS} > semanticautomation_cr_backup_<date>.yaml

    Where <date> is the date you are applying the patch.

  2. Run the following command to apply the patch to the Semantic Automation CR (semanticautomation-cr):

    oc patch semanticautomation semanticautomation-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"image_digests":{
    "semantic_automation_service_image": "sha256:ce919c28aed1fd8a8a7768daf73633f82bb4f526605c6e7aa752cb85e99a7efb",
    "semantic_inference_service_image": "sha256:da3f753a6b3f6644821c9a1684b87fe6be5b4d331c30ca866d8640a4ee83516e"
}}}'

  3. Wait for the Semantic Automation operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get semanticautomation semanticautomation-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the updated images.


For Data Privacy (if installed)

  1. Save a copy of the Data Privacy custom resource (CR) currently deployed on the cluster:

    oc get dp dp-cr -o yaml -n ${PROJECT_CPD_INST_OPERANDS} > dp_cr_backup_<date>.yaml

    where <date> is the date you are applying the patch.

  2. Run the following command to apply the patch to the Data Privacy CR (dp-cr):

    oc patch dp dp-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"image_digests":{
    "dp_ui_image": "sha256:d54d00d45fea9860a1fa523cc61ef026117bf943a5d8f9b8930afdd72fa68275" 
}}}'

  3. Wait for the Data Privacy operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get dp dp-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pod in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the updated image.

Manta Data Lineage (if installed)

  1. Save a copy of the Data Lineage custom resource (CR) currently deployed on the cluster:

    oc get datalineage datalineage-cr -o yaml -n ${PROJECT_CPD_INST_OPERANDS} > manta_data_lineage_cr_backup_<date>.yaml

    Where <date> is the date you are applying the patch.

  2. Run the following command to apply the patch to the Data Lineage CR (datalineage-cr):

    oc patch datalineage datalineage-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=merge -p '{"spec":{"datalineage_scanner_service_image": {"name":"lineage-scanner-service@sha256", "tag":"93451ab8c54d48caab31081513a293e2240e76052a47dbf01a407f6902051f7e","tag_metadata":"8.1.18-amd64"}}}'

  3. Wait for the Data Lineage operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get datalineage datalineage-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pod in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the updated image.

 

Reverting the hotfix

Make sure to revert the image overrides before you install or upgrade to a newer refresh or a major release of IBM Cloud Pak for Data.  

 

For CCS

  1. Run the following command to remove the image digest updates from the Common Core Services custom resource:

    oc patch ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=json --patch '[{"op":"remove","path":"/spec/image_digests/wdp_connect_connection_image"},{"op":"remove","path":"/spec/image_digests/wdp_connect_connector_image"},{"op":"remove","path":"/spec/image_digests/wdp_connect_flight_image"}]'

  2. Wait for CCS operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get ccs ccs-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the original image.

For IKC, IKC Standard/Premium, or watsonx.data intelligence

  1. View the helm chart update history and there should be a new revision from the previous upgrade command:

    helm history -n ${PROJECT_CPD_INST_OPERANDS} wkc

  2. Run the following command to roll back to the previous revision:

    helm rollback wkc 1 -n ${PROJECT_CPD_INST_OPERANDS}

  3. Wait for WKC operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get wkc wkc-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the original images.

For Data Privacy (if installed)

  1. Run the following command to remove the image digest updates from the Data Privacy custom resource:

    oc patch dp dp-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=json --patch '[{"op":"remove","path":"/spec/image_digests/dp_ui_image"}]'

  2. Wait for Data Privacy operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get dp dp-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pod in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the original image.

For Data Lineage (if installed)

  1. Run the following command to remove the image digest updates from the Data Lineage custom resource:

    oc patch datalineage datalineage -n ${PROJECT_CPD_INST_OPERANDS} --type=json --patch '[{"op":"remove","path":"/spec/image_digests/datalineage_scanner_service_image"}]'

  2. Wait for Data Lineage operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get datalineage datalineage-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pod in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the original image.

For Semantic Automation (if IKC Standard or IKC Premium is installed)

  1. Run the following command to remove the image digest updates from the Semantic Automation custom resource:

    oc patch semanticautomation semanticautomation-cr -n ${PROJECT_CPD_INST_OPERANDS} --type=json --patch '[{"op":"remove","path":"/spec/image_digests/semantic_automation_service_image"},{"op":"remove","path":"/spec/image_digests/semantic_inference_service_image"}]'

  2. Wait for Semantic Automation operator reconciliation to complete. Run the following command to monitor the reconciliation status:

    oc get semanticautomation semanticautomation-cr -n ${PROJECT_CPD_INST_OPERANDS}

    After a period of time, the patched pods in ${PROJECT_CPD_INST_OPERANDS} should be up and running with the original images.

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRNZNM","label":"IBM watsonx.data intelligence"},"ARM Category":[{"code":"a8mgJ00000008NNQAY","label":"watsonx.data intelligence"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.0"}]

Document Information

Modified date:
09 January 2026

UID

ibm17254566

Page Feedback