- Identify the pull image for the release. For example, for the latest OCP 4.4.x the
release.txtfor the corresponding release. For example here: https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest-4.4/release.txt
In this example, the latest 4.4.x it is 4.4.3 and it has this entry:
Pull From: quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc
Validate your current version is in the list of upgrade path for the desired release. For 4.4.3 these are the possible upgrade paths:
Upgrades: 4.3.18, 4.3.19, 4.3.20, 4.3.21, 4.4.0-rc.0, 4.4.0-rc.1, 4.4.0-rc.2, 4.4.0-rc.4, 4.4.0-rc.6, 4.4.0-rc.7, 4.4.0-rc.8, 4.4.0-rc.9, 4.4.0-rc.10, 4.4.0-rc.11, 4.4.0-rc.12, 4.4.0-rc.13, 4.4.0, 4.4.1, 4.4.2
- That is the pull image to use for the explicit upgrade:
export PULL_IMAGE=quay.io/openshift-release-dev/ocp-release@sha256:039a4ef7c128a049ccf916a1d68ce93e8f5494b44d5a75df60c85e9e7191dacc
# WARNING: This option does not check for upgrade compatibility and may break your cluster
oc adm upgrade --allow-explicit-upgrade --to-image=${PULL_IMAGE}
- To monitor progress use the following commands:
oc get clusterversion
oc get co
# to combine their output in the console:
watch -c "oc get clusterversion ; oc get co"