Update from 1.3.3 to 1.4.0/1.4.0-H1

You can update your existing CDP Private Cloud Data Services 1.3.3 to 1.4.0 or 1.4.0-H1 without requiring an uninstall. After the update is complete, you can then upgrade the underlying OpenShift Container Platform from 4.5.x or 4.6.x to 4.7.x or 4.8.x.

Ensure that you have the following before you update:

Ensure that this kubeconfig has permissions to create Kubernetes namespaces.
Back up all the external databases used by CDP Private Cloud Data Services 1.3.3.
CDP Private Cloud Base 7.1.6 or higher with a Data Lake cluster
Cloudera Manager 7.6.5
Single instance of CDP Private Cloud Data Services 1.3.3 installed on your OCP cluster
One or more environments registered in CDP Private Cloud Data Services 1.3.3
One of the registered environment has one or more Cloudera Data Warehouse (CDW) or Cloudera Machine Learning (CML) experience workspaces
Kubeconfig file for the OCP 4.7 or 4.8 cluster
Access to the Cloudera Private Cloud repositories (archive.cloudera.com)
Administrator access to OCP 4.7 or 4.8 and Privileged access to your external Vault
note
There is no direct upgrade from 1.0, 1.1, 1.2, 1.3.1, or 1.3.2 to 1.4.0/1.4.0-H1.

In Cloudera Manager, navigate to CDP Private Cloud Data Services 1.3.3 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, upload a Kubernetes configuration (kubeconfig) file from your existing environment. You can obtain this file from your OpenShift Container Platform administrator. Click Continue.
On the Update Progress page, you can see the progress of your update. Click Continue.
important
During the "Upgrade Control Plane" step of the CDP upgrade process, the grafana pod can get stuck in the terminating sate. This usually means that all other 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 ECS Server host:
<grafana-pod-id> --force --grace-period=0
important
If are upgrading in an air gapped environment and the upgrade has stalled, query the cluster upgrade status by running the following command from a gateway node with a valid kubeconfig file:
```
oc get clusterversion
```
If you encounter an error message similar to:
```
Insights Operator is degraded in a restricted network OCP cluster
```
disable the Insights Cluster Operator as described in the OpenShift documentation: Opting out of remote health reporting.
important
If the upgrade does not complete:
1. If you see a messages similar to the following in the upgrade command output in the Cloudera Manager Admin Console:
  cdp-release-grafana-57d964df67-qm4hv 0/3 Terminating 0 61m cdp-release-grafana-79fd889784-47z8v 3/3 Running 0 17m
2. Force delete the pod that is shown as Terminating in the log message:
  kubectl delete pods <pod name and nubmer as shown in the error message> --grace-period=0 --force
3. Resume the upgrade.
After the update is complete, the Summary page appears. You can now Launch CDP Private Cloud from here.

Or you can navigate to the CDP Private Cloud Data Services page and click Open CDP Private Cloud Data Services.

CDP Private Cloud Data Services opens up in a new window.
After the update is complete, upgrade the underlying OpenShift Container Platform from 4.5.x or 4.6.x to 4.7.x or 4.8.x.