OCNADD Upgrade

This section includes information about upgrading an existing OCNADD deployment.

When you attempt to upgrade an existing OCNADD 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.

Important:

(Optional) A timeout interval of 15 minutes can be set while performing an upgrade as only one POD of the Data Director services is upgraded at a time.
Ensure that no OCNADD pod is in the failed state
Ensure that the defined in the Preupgrade Tasks are complete
There can be a downtime of Kafka brokers for about a minute while performing an upgrade that affects all of the brokers. You can avoid this downtime by upgrading the brokers one at a time, if applicable. Kafka upgrade along with PVC storage changes are not supported.
The Consumer Adapter and Egress gateway pods/services are created when Data feed is created from OCNADD GUI. By default, the upgrade of these pods is set to false. To upgrade the Consumer Adapter and Egress gateway services, see the "Parameter Updates for OCNADD Microservices" section of the Oracle Communications Network Analytics Data Director User Guide .

Execute the following command to upgrade an existing OCNADD deployment:

Upgrade the OCNADD microservices:
- When using the local Helm chart:
```
 helm upgrade <release_name> <helm_chart> --namespace <namespace-name> --timeout=15m
```
  where,
  
  <release_name> is the release name used by the Helm command
  
  <helm_chart> is the location of the Helm chart extracted from the target ocnadd-<releaseNumber>.tgz file
  
  <namespace-name> is the OCNADD namespace in which the release is deployed
- When using the chart from Helm repo:
```
 helm upgrade <release_name> <helm_repo/helm_chart> --version <chart_version> --namespace <namespace-name> --timeout=15m
```
  where,
  
  <helm_repo> is the OCNADD Helm repo.
  
  <chart_version> is the version of the Helm chart extracted from the ocnadd-<releaseNumber>.tgz file
  
  <namespace-name> is the OCNADD namespace in which the release is deployed
Check the status of the upgrade:
```
helm history <release_name> --namespace <namespace-name>
```
In case of any failure, follow the steps mentioned in the Oracle Communications Network Analytics Data Director Troubleshooting Guide.