Upgrade: Openshift Operator Online



Check if a new version is available from the OperatorHub

Take the following steps to check if a new version is available from the OperatorHub when compared with the installed version

  1. Log into the OpenShift Admin Console
  2. In the left-hand sidebar, select Operators > OperatorHub
  3. In the search bar of the center pane, search for vfunction
  4. Select the vFunction Operator with the Certified tag in the top-right corner. The Operator should also have an Installed green check in the bottom center of the display box as well
  5. Check the Version available in the left-hand sidebar of the selected vFunction Operator, e.g. 4.0.1594
  6. Click the View it here link inside the blue text box that says, “Installed Operator: This Operator has been installed on the cluster”
  7. In the center pane’s tabs, select the vFunction tab
  8. In the center pane, click the link for the vfunction-server
  9. In the center pane’s right-hand column, check the version of the Container Images, e.g. registry.connect.redhat.com/vfunction/vfunction-mysql:v3.8.1535, to see if the available version from Step #5 is the same version as the Container Images

Upgrade Steps

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