4 Upgrading OCNRF
This section includes information about upgrading an existing OCNRF deployment.
Note:
IF YOU HAVE ENABLED SERVICE MESH THEN YOU HAVE TO PERFORM FRESH INSTALLATION OF OCNRF. YOU CANNOT UPGRADE FROM OCNRF 1.7.0 TO OCNRF 1.7.2.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.
ocnrf-custom-values-1.7.2.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.7.2 upgrade supports changing HELM configurable parameters only.$ 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.7.2.yaml
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
|
- Check the history of helm
deployment:
helm history <helm_release>
- Rollback to the required
revision:
helm rollback <release name> <revision number>