Skip to content

Latest commit

 

History

History
55 lines (46 loc) · 3.21 KB

upgrading-mtv-ui.adoc

File metadata and controls

55 lines (46 loc) · 3.21 KB

Upgrading {the-lc} {project-full}

You can upgrade the {operator-name} by using the {ocp} web console to install the new version.

Procedure
  1. In the {ocp} web console, click OperatorsInstalled Operators{operator-name-ui}Subscription.

  2. Change the update channel to the correct release.

  3. Confirm that Upgrade status changes from Up to date to Upgrade available. If it does not, restart the CatalogSource pod:

    1. Note the catalog source, for example, redhat-operators.

    2. From the command line, retrieve the catalog source pod:

      $ {oc} get pod -n openshift-marketplace | grep <catalog_source>
    3. 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.

  4. If you set Update approval on the Subscriptions tab to Manual, approve the upgrade.

  5. 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 to Critical. For more information, see Adding a VMSphere source provider.

  6. If you mapped to NFS on the {ocp} destination provider in {project-short} 2.2, edit the AccessModes and VolumeMode parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see Customizing the storage profile.