Upgrading Cloudera Data Services on premises using OpenShift Container Platform

After the upgrade process is complete, you may need to upgrade the underlying OpenShift Container Platform. For more information about the supported OpenShift Container Platform versions, see the Software Support Matrix for OpenShift.

You can upgrade Cloudera Data Services on premises 1.5.4 SP2, 1.5.5, or 1.5.5 SP1 to 1.5.5 SP2, 1.5.5 SP2 CHF1 versions without uninstalling the existing installation.

Review the Software Support Matrix for OpenShift.
Make a backup of the OpenShift routes before upgrading to 1.5.5 SP2 CHF1.
To upgrade Cloudera Data Engineering, make sure that you have performed Pre-upgrade - Upgrading Cloudera Data Engineering service with endpoint stability and taken a backup of the Cloudera Data Engineering service.

Ensure that you have the following before you upgrade:

A kubeconfig file for the OpenShift Container Platform cluster.
Ensure that the kubeconfig file has permissions to create Kubernetes namespaces.
Back up all of the external databases used by Cloudera Data Services on premises.
One or more environments registered in Cloudera Data Services on premises.
One of the registered environment has one or more Cloudera Data Warehouse or Cloudera AI experience workspaces.
Access to the Cloudera on premises repositories (archive.cloudera.com).
Administrator access to OpenShift Container Platform and Privileged access to your external Vault.

In Cloudera Manager, navigate to Cloudera Data Services on premises and click . Click Update.
On the Getting Started page, you can select the Install method - Air Gapped or Internet and proceed.

Internet install method

Air Gapped install method

Click Continue.
On the Collect Information page and click Next.
For the kubeconfig upload step (collect information) : After we upload the KUBECONFIG file:
- If you are using non default repository, confirm all the images are uploaded.
- In the Ingress Certificate Secret Synchronization section, enter the name of the TLS secret located in the openshift-ingress namespace into the OpenShift Ingress Secret Name field. This is the default certificate used by the OpenShift cluster, and it will be used by the Istio ingress for TLS termination.
- If you are using External Vault, provide the details with respect to Vault Address and Token information with respect to the External Vault.
On the Update Data Services page, you can see the progress of your upgrade. Click Next.
important
During the "Upgrade Cloudera Control Plane" step of the Cloudera upgrade process, the grafana pod can get stuck in the terminating sate. This usually means that all other Cloudera Control Plane pods are in the running state, but for grafana, there is one pod that is in running state and there is one pod that is stuck in terminating state. The terminating pod has the following message:
containers with incomplete status: [multilog-init grafana-sc-datasources]
If you search for the terminating pod id in the kubelet log on the host, the following error message can be found:
E0531 2209 kuberuntime_sandbox.go:70] CreatePodSandbox for pod "<pod id>" failed: rpc error: code = Unknown desc = error reading container (probably exited) json message: EOF
If there is a granfa pod stuck in terminating state, run the following command on the Cloudera Embedded Container Service Server host:
<grafana-pod-id> --force --grace-period=0
After the upgrade is complete, the Summary page appears. You can now Launch Cloudera on premises from here.

Or you can navigate to the Cloudera Data Services on premises page and click Open Cloudera on premises.

Cloudera Data Services on premises opens up in a new window.

After upgrade, the Cloudera Manager admin role may be missing the Host Administrators privilege in an upgraded cluster. The cluster administrator should run the following command to manually add this privilege to the role.
```
ipa role-add-privilege <cmadminrole> --privileges="Host Administrators"
```