Cloud Pak for Data

oc get po --no-headers --all-namespaces -o wide| grep -Ev '([[:digit:]])/\1.*R' | grep -v 'Completed'

Actually, as mentioned in the section 5)Evaluate and decide the time window of the article Pre-upgrade tasks for CPD upgrade, the end-users are recommended to stop their own environment runtimes and scheduled jobs before the upgrade. But we'd better take following actions to make sure that environment runtimes and scheduled jobs are stopped or suspended.

List the active environment runtimes firstly

for mydeploy in $(oc get deploy -l created-by=spawner --no-headers| awk '{print $1}') ; do echo $mydeploy; done

Stop the active environment runtimes

for mydeploy in $(oc get deploy -l created-by=spawner --no-headers| awk '{print $1}') ; do oc delete deployment $mydeploy; done

For example, your current OpenShift version is 4.5.X and you plan to upgrade it to 4.8.  Your upgrade path would be 4.5.X -> 4.6.Y -> 4.7.Z -> 4.8.N.

b) When upgrading OpenShift,  subscribe to the EUS channel for getting the EUS support if it's available.
For example, the OCP 4.6 support has been End of Support.  But the Extended Update Support of OCP 4.6 (4.6-EUS) support is still available. If you still want to stay on OCP 4.6 with support, then you'll have to update the your OpenShift cluster's OCP channel to EUS-4.6.
For more information,  please refer to the OpenShift's lifecycle policy.
c)Validate the OpenShift cluster status
Make sure the cluster operator are in healthy status
oc get co
Make sure all the nodes are in Ready status
oc get nodes
Make sure all the machine configure pool are in healthy status.
oc get mcp

6) Storage upgrade
When upgrading from Cloud Pak for Data 3.5 to 4.0, if you are running an unsupported version of Red Hat® OpenShift® Container Storage or Portworx, you must upgrade your storage before you upgrade to IBM® Cloud Pak for Data Version 4.0. For information about supported versions of shared persistent storage, see Storage requirements.

7)Cloud Pak for Data platform and services upgrade
Different services may have different prerequisites and procedures for the upgrade from 3.5 to 4.0. For example, some services (e.g. Data virtualization) require that you create the Db2U operator subscription manually while some others not. And for some Watson services (e.g. Watson Discovery, Watson Assistant), you may have to enable the License Service of the IBM Cloud Pak Foundational service.

There maybe service instances provisioned for some particular services, such as Spark instance, Data Virtualization instance, Db2WH instance. For these kind of services, apart from upgrade the services themselves, you also need to upgrade the service instances accordingly.

Record the commands and the corresponding results during the upgrade. After each service upgrade done, make sure it is in healthy status before you proceeding to next upgrade of another service.