4 Upgrading OCNRF

This section includes information about upgrading an existing OCNRF deployment.

Note:

OCNRF upgrade is supported only within the same release for updating helm configuration.

When you attempt to upgrade an existing OCNRF deployment, the running set of containers and pods are replaced with the new set of containers and pods. However, If there is no change in the pod configuration, the running set of containers and pods are not replaced.

If you need to change any configuration then change the ocnrf-custom-values-1.8.0.yaml file with new values.

Note:

It is advisable to create a backup of the file before changing any configuration.

To configure the parameters, see section OCNRF Configuration.

Caution:

OCNRF 1.8.0 upgrade supports changing HELM configurable parameters only.

Execute the following command to upgrade an existing OCNRF deployment:

1. For helm 2, execute the following command:

   $ helm upgrade <release> <helm chart> [--version <OCNRF version>] -f <ocnrf_customized_values.yaml>

   For example:

   $ helm upgrade <release> <helm chart> [--version <OCNRF version>] -f ocnrf-custom-values-1.8.0.yaml

2. For helm 3, execute the following command:

   $ helm3 upgrade <release> <helm chart> [--version <OCNRF version>] -f <ocnrf_customized_values.yaml> --namespace <namespace-name>

To check the status of the upgrade, execute:

helm status <helm-release>

For example: helm status ocnrf

Table 4-1 Parameters and Definitions during OCNRF Upgrade

Parameters	Definitions
<helm chart>	It is the name of the chart that is of the form <repository/ocnrf>. For example: reg-1/ocnrf or cne-repo/ocnrf
<release>	It can be found in the output of helm list command

In case of backout:

1. Check the history of helm deployment:

   helm history <helm_release>

2. Rollback to the required revision:

   helm rollback <release name> <revision number>