Upgrading Guardium Insights manually

You can upgrade Guardium® Insights manually or by using the all-in-one script.

About this task

Use the following procedure to manually upgrade Guardium Insights. If you are upgrading Guardium Insights by using the all-in-one script, you can skip this procedure.

Procedure

  1. Switch to namespace for the Guardium Insights deployment.
    oc project ${NAMESPACE}
  2. Run the preinstall script. This script sets up secrets and parameters for the Guardium Insights instance.
    export GI_INVENTORY_SETUP=install
  3. Install the Guardium Insights catalog.
    oc ibm-pak launch $CASE_NAME \
--version $CASE_VERSION \
--inventory $GI_INVENTORY_SETUP \
--action install-catalog \
--namespace openshift-marketplace \
--args "--inputDir ${LOCAL_CASE_DIR}"
  4. Verify that the catalogs are installed.
    oc get pods -n openshift-marketplace
    The output is similar to the following example.
    NAME                                                     READY   STATUS      RESTARTS       AGE
ibm-cert-manager-catalog-gsdpq                           1/1     Running     0              30m
ibm-cloud-databases-redis-operator-catalog-xlsbk         1/1     Running     0              31h
ibm-db2uoperator-catalog-d5vp5                           1/1     Running     0              41s
ibm-guardium-insights-operator-catalog-lb2sn             0/1     Running     0              29s
ibm-redis-cp-operator-catalog-ljn58                      1/1     Running     0              164m
  5. Install the operator.
    oc ibm-pak launch $CASE_NAME \
--version $CASE_VERSION \
--inventory $GI_INVENTORY_SETUP \
--action install-operator \
--namespace ${NAMESPACE} \
--args "--registry cp.icr.io --user ${CP_REPO_USER} --pass ${CP_REPO_PASS} --secret ibm-entitlement-key --inputDir ${LOCAL_CASE_DIR}"
  6. Verify the cluster service version for Guardium Insights is present.
    oc get csv -w
    The output is similar to the following example.
    NAME                                          DISPLAY                                                         VERSION      REPLACES                                      PHASE
cloud-native-postgresql.v1.18.12              EDB Postgres for Kubernetes                                     1.18.12      cloud-native-postgresql.v1.18.10              Succeeded
db2u-operator.v110509.0.2                     IBM Db2                                                         110509.0.2   db2u-operator.v110509.0.1                     Succeeded
ibm-cert-manager-operator.v4.2.7              IBM Cert Manager                                                4.2.7        ibm-cert-manager-operator.v4.2.1              Succeeded
ibm-cloud-databases-redis.v1.6.5              IBM Operator for Redis                                          1.6.5        ibm-cloud-databases-redis.v1.6.4              Succeeded
ibm-common-service-operator.v4.6.5            IBM Cloud Pak foundational services                             4.6.5        ibm-common-service-operator.v4.5.0            Succeeded
ibm-commonui-operator.v4.4.4                  Ibm Common UI                                                   4.4.4        ibm-commonui-operator.v4.3.1                  Succeeded
ibm-events-operator.v5.0.1                    IBM Events Operator                                             5.0.1        ibm-events-operator.v4.9.0                    Succeeded
ibm-guardium-insights-operator.v3.5.0         IBM Security Guardium Insights for IBM Cloud Pak for Security   3.5.0        ibm-guardium-insights-operator.v3.4.0         Succeeded
ibm-iam-operator.v4.5.4                       IBM IM Operator                                                 4.5.4        ibm-iam-operator.v4.4.0                       Succeeded
ibm-mongodb-operator.v4.2.2                   IBM MongoDB Operator                                            4.2.2                                                      Succeeded
ibm-redis-cp.v1.1.9                           ibm-redis-cp-operator                                           1.1.9                                                      Succeeded
ibm-zen-operator.v5.1.7                       IBM Zen Service                                                 5.1.7                                                      Succeeded
operand-deployment-lifecycle-manager.v4.3.4   Operand Deployment Lifecycle Manager                            4.3.4
  7. Verify that the operators are installed.
    oc get pods -n ${NAMESPACE}
    The output is similar to the following example.
    NAME                                                       READY   STATUS      RESTARTS   AGE
db2u-day2-ops-controller-manager-75ff8777ff-4mhjb          1/1     Running     0          5m25s
db2u-operator-manager-f59c45f99-9t7m5                      1/1     Running     0          5m25s
ibm-cloud-databases-redis-operator-844bb8cf74-bt6hg        1/1     Running     0          31h
ibm-guardium-insights-operator-57f5b589f9-tlpmw            1/1     Running     0          163m
mongodb-kubernetes-operator-774f855cbc-gjr4r               1/1     Running     0          49s
  8. Prepare for a Guardium Insights upgrade.
    1. Update the Guardium Insights custom resource file by using the following command.
      oc edit guardiuminsights -n=${NAMESPACE}
    2. Change the version to 3.5.0.
    3. Change the license.licenseType to L-YRPR-ZV3BA6.
    4. Change the guardiumInsightsGlobal.insights.ics.namespace to GI_NAMESPACE.
    5. If the following entry is in your custom resource (CR) file, remove it.
      ssh-service: serviceAccount: insights-odf-ssh-service-sa
    6. Monitor the reconciliation by using the following command.
      oc get guardiuminsights –w
      In the following output example, the DESIRED_VERSION is updated to 3.5.0. The displayed versions in the output vary based on the Guardium Insights version that you want to upgrade to and the current version on your system.
      NAME      TYPE      STATUS   REASON       MESSAGE                   DESIRED_VERSION   INSTALLED_VERSION
staging   Ready     True     Complete     Completed Reconciliation   3.5.0            3.5.0            

What to do next

After you upgrade the Cloud Pak foundational services version, you can remove the older version of Cloud Pak foundational services by completing the following steps.