Upgrading privileged monitors (Upgrading from Version 4.8 to Version 5.0)

Privileged monitors provide additional information about the health of the cluster and resources that are not typically included in the platform monitors. If you installed the privileged monitors in Cloud Pak for Data Version 4.8, a cluster administrator must upgrade the monitors as part of the upgrade to Version 5.0. If you want to add the privileged monitors to the instance that you are upgrading, a cluster administrator must install the privileged monitoring service.

Upgrade phase
  • You are not here. Updating your cluster
  • You are not here. Updating your client workstation
  • You are not here. Collecting required information
  • You are not here. Preparing to run an upgrade in a restricted network
  • You are not here. Preparing to run an upgrade from a private container registry
  • You are not here. Installing and upgrading prerequisite software
  • You are not here. Updating the shared cluster components
  • You are here icon. Preparing to upgrade an instance of Cloud Pak for Data
  • You are not here. Upgrading an instance of Cloud Pak for Data
Who needs to complete this task?

Cluster administrator A cluster administrator must complete this task.

When do you need to complete this task?
Complete this task if either of the following statements are true:
  • You installed the privileged monitoring service on Cloud Pak for Data Version 4.8 and you need to upgrade the service.
  • You want to add privileged monitors to your Cloud Pak for Data deployment.

Repeat as needed If you have multiple instances of Cloud Pak for Data, repeat this task for each instance of Cloud Pak for Data where you want to use privileged monitors.

Before you begin

The privileged monitoring service is installed in a separate project from Cloud Pak for Data. The privileged monitoring service is installed once on the cluster and is used by any instances of Cloud Pak for Data that are integrated with the privileged monitoring service.

New installations only:

Before you install the privileged monitoring service for the first time, ensure that the project where you plan to install the privileged monitoring service exists. The apply-privileged-monitoring-service command cannot create the project.

The recommended project name is ibm-cpd-privileged. You can use any Red Hat® OpenShift® project, but do not co-locate the privileged monitoring service with other software.

Best practice: You can run the commands in this task exactly as written using the installation environment variables. Ensure that you added the new environment variables from Updating your environment variables script.

In addition, ensure that you source the environment variables before you run the commands in this task.

About this task

The following events are available when you upgrade the privileged monitoring service:

Cluster operator status check (check-cluster-operator-status)
Checks the status of the cluster operators that comprise the Red Hat OpenShift Container Platform infrastructure to determine whether:
  • All of the operators are AVAILABLE
  • Any of the operators are DEGRADED
Network status check (check-network-status)
Checks the status of the PodNetworkConnectivityCheck objects for cluster resources to determine whether the objects are Reachable.
Node imbalance status check (check-node-imbalance-status)
Checks whether vCPU requests are balanced across nodes or whether one node is supporting a disproportionately high load.
Node status check (check-node-status)
Checks whether the nodes on the cluster are ready and whether the nodes are using too many resources.
Volume usage status check (check-volume-status)
Checks whether the persistent volume claims associated with the deployment are running out of space.
Restriction: Only persistent volume claims that are mounted by a running pod are monitored.
Operator namespace status check (check-operator-namespace-status)
Checks whether the resources in the operators project for the deployment are healthy.
Important: If you also want to check the status of the operators in the project where the scheduling service is installed, you must run the apply-privileged-monitoring-service command with the --cluster_components_ns=${PROJECT_SCHEDULING_SERVICE} option.
EDB cluster status check (check-edb-cluster-status)
Checks whether any instances of EDB Postgres that are associated with the deployment are healthy. For example, whether the database that Cloud Pak for Data uses to store metadata for the deployment is healthy.

Run the apply-privileged-monitoring-service command to upgrade the privileged monitors for an instance of Cloud Pak for Data.

Procedure

To upgrade the privileged monitoring service:

  1. Log the cpd-cli in to the Red Hat OpenShift Container Platform cluster:
    ${CPDM_OC_LOGIN}
    Remember: CPDM_OC_LOGIN is an alias for the cpd-cli manage login-to-ocp command.
  2. Upgrade the privileged monitors.

    The command that you run depends on whether you want the Operator namespace status check to include information about the scheduling service.


    Include only information about the operators project
    cpd-cli manage apply-privileged-monitoring-service \
    --privileged_service_ns=${PROJECT_PRIVILEGED_MONITORING_SERVICE} \
    --cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS}

    Include information about the operators project and the scheduling service project
    cpd-cli manage apply-privileged-monitoring-service \
    --privileged_service_ns=${PROJECT_PRIVILEGED_MONITORING_SERVICE} \
    --cluster_components_ns=${PROJECT_SCHEDULING_SERVICE} \
    --cpd_operator_ns=${PROJECT_CPD_INST_OPERATORS} \
    --cpd_instance_ns=${PROJECT_CPD_INST_OPERANDS}

    The monitors are updated for the specified instance of Cloud Pak for Data.

    If the privileged monitoring service was is not already installed, the privileged monitoring service is installed in the PROJECT_PRIVILEGED_MONITORING_SERVICE project.

What to do next

Now that you've installed the privileged monitors, you're ready to complete Installing the IBM Cloud Pak for Data configuration admission controller webhook (Upgrading from Version 4.8 to Version 5.0).