You can upgrade the {operator-name} by using the {ocp} web console to install the new version.
-
In the {ocp} web console, click Operators → Installed Operators → {operator-name-ui} → Subscription.
-
Change the update channel to the correct release.
-
Confirm that Upgrade status changes from Up to date to Upgrade available. If it does not, restart the
CatalogSource
pod:-
Note the catalog source, for example,
redhat-operators
. -
From the command line, retrieve the catalog source pod:
$ {oc} get pod -n openshift-marketplace | grep <catalog_source>
-
Delete the pod:
$ {oc} delete pod -n openshift-marketplace <catalog_source_pod>
Upgrade status changes from Up to date to Upgrade available.
If you set Update approval on the Subscriptions tab to Automatic, the upgrade starts automatically.
-
-
If you set Update approval on the Subscriptions tab to Manual, approve the upgrade.
-
If you are upgrading from {project-short} 2.2 and have defined VMware source providers, edit the VMware provider by adding a VDDK
init
image. Otherwise, the update will change the state of any VMware providers toCritical
. For more information, see Adding a VMSphere source provider. -
If you mapped to NFS on the {ocp} destination provider in {project-short} 2.2, edit the
AccessModes
andVolumeMode
parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see Customizing the storage profile.