5 Upgrading an Existing ProvGateway Deployment

In this section, you will learn to upgrade an existing Provisioning Gateway Deployment.

Note:

IF YOU HAVE ENABLED SERVICE MESH THEN YOU HAVE TO INSTALL PROVISIONING GATEWAY. YOU CANNOT UPGRADE FROM PROVGW 1.7.0 TO PROVGW 1.7.1. HOWEVER, IF THE SERVICE MESH IS NOT ENABLED THEN YOU CAN UPGRADE FROM PROVGW 1.7.0 TO PROVGW 1.7.1 BY FOLLOWING THE HELM UPGRADE SECTION.

Upgrading an existing deployment replaces the running containers and pods with new ones. If there is no change in the pod configuration, the pods are not replaced. Unless there is a change in the service configuration of a microservice, the service endpoints remain unchanged (ClusterIP etc.).

Note:

You should stop the provisioning traffic while upgrading the Provisioning Gateway and then, perform the helm upgrade.

Helm Upgrade

To upgrade Provisioning Gateway via Helm:

• Follow the deployment instructions provided in the Installation Sequence section for extracting the required Provisioning Gateway software components and if required, re-tag and push the images to customer's repository.
• Take a backup of the provgw-custom-values-1.7.0.yaml file and modify the parameters as per site requirement.
• Execute the following command to upgrade an existing Provisioning Gateway deployment. For the parameters that are configurable, see Customizing Provisioning Gateway.

  $ helm upgrade <release> <helm chart> [--version <ProvGw version>] -f <provgw-custom-values-1.7.0.yaml>

  In the above command:

  • <release> information is available in the output of 'helm list' command.
  • <chart> is the name of the chart in the form of <repository/provgw> . Example: reg-1/provgw or cne-repo/provgw

Rollback Instructions

As it is an initial release of Provisioning Gateway, rollback feature is not applicable. However, you can use helm del on the newly created task.