Upgrade: Openshift Operator Offline

Mirror OpenShift Container Platform image repository to an offline repository

Follow the OpenShift documentation to mirror the OCP image repository to your offline repository.

Upgrade using the OpenShift Management Console

Take the following steps to upgrade an OpenShift Operator and underlying Operand (the Backend and UI of the vFunction Server) that is online.

  1. Log into the OpenShift Admin Console
  2. In the left-hand sidebar, select Operators > Installed Operators
  3. From the list of installed Operators in the center pane, search for and select vFunction Operator
  4. In the center pane’s tabs, select the vFunction tab
  5. In the center pane, click the link for the vfunction-server
  6. In the center pane’s tabs, select the YAML tab
  7. Search for the subkey upgrade under spec. This key should be around Line 285 in the YAML
  8. Change the value from Never to Always. This changes the automatic upgrade mechanism from Off to a workflow where the Operator checks for a new version every 10 minutes and installs the new version automatically
  9. In the left-hand sidebar, go to Workloads > Pods
  10. The environment’s Pods should go through Status: Terminating as the Pods from the previous version are taken down and Status: Running as the new Pods are brought online
  11. Once the vfunction-nginx Pod is ready, the upgrade has completed
  12. Once the upgrade has completed, change the upgrade subkey from Step #7 back to Never

Upgrade using the OC Command Line Tool

  1. Open the vFunction Cluster Resource in the OC Editor
oc edit vfunctionserver vfunction-server -n <namespace>
  1. Search for the subkey upgrade under spec. This key should be around Line 285 in the YAML
  2. Change the value from Never to Always. This changes the automatic upgrade mechanism from Off to a workflow where the Operator checks for a new version every 10 minutes and installs the new version automatically
  3. Check for the status of the Pods in the environment. The environment’s Pods should go through Status: Terminating as the Pods from the previous version are taken down and Status: Running as the new Pods are brought online
oc get pods -n <namespace>
  1. Once the vfunction-nginx Pod is ready, the upgrade has completed
  2. Once the upgrade has completed, change the upgrade subkey from Step #3 back to Never

Updated on 03 Apr 2025