8 Upgrading an Existing ProvGateway Deployment

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

Note:

You can upgrade from ProvGateway 1.7.1 to ProvGateway 1.8.0

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.8.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.8.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

Execute the following command to check whether pods are running successfully:

kubectl get pods -n <namespace_name>

If there are issues that you cannot recover on checking logs and describe on pods, then you have to do image rollback using Helm. The steps are as follows:

• Use the backed up customized previous version's <provgw-values.yaml> file to roll back to the previous version.
• Execute the helm rollback command, helm rollback <helm release name> <revision_no>.

  Note:

  To obtain the revision number, execute this command: helm history <helm release name>