Go to primary content
Oracle® Communications Network Exposure Function (NEF) Cloud Native Installation and Upgrade Guide
Release 1.0
F16986-01
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

4 Upgrading Network Exposure Function

User can perform the helm upgrade command in the following scenarios.

  • Update an existing parameter setting, such as global.imageTag, global.envMysqlHost.etc.,
  • Add more parameters per requirement

To update Binding Support Function services, execute the following command and specify the upgrade parameter:

helm upgrade <NAME>-nef \

--set global.envMysqlHost=<MYSQL_HOST>,global.envMysqlUser=nefusr,global.envMysqlPassword=nefpasswd \

--set global.envJaegerAgentHost=<JAEGER_SERVICE>.<JAEGER_SERVICE_NAMESPACE> \

--set global.envManageNF=NEF,global.envSystemName=NEF,common.configmapApplicationConfig.nrfClientType=NEF \

--set global.imageTag=<IMAGE_TAG>,global.dockerRegistry=<DOCKER_REGISTRY_ADDRESS> \

--set platform.enabled=true,pcf.enabled=false,bsf.enabled=false,common.enabled=true,nef.enabled=true \

--set common.deploymentNrfClientservice.envNamespace=<NAMESPACE>-nef,platform.appinfo.topic=NRF.UDM \

./<HELM_CHART_NAME_WITH_EXTENSION>

Note:

<NAME> and <NAMESPACE> must be same as helm install command.

Note:

The upgrade command is similar to install command, because, if user do not specify the same parameters for both upgrade and install, then the settings applied by install command may lost and use default settings from values.yaml file for missing parameters in upgrade command.

For specific deployments, the few parameters cannot be updated. Table 4-1 provides the details of parameters.

Table 4-1 Parameters for Deployment

Deployment Parameters Description
NEF platform.enabled=true,pcf.enabled=false,bsf.enabled=false,common.enabled=true,nef.enabled=true For NEF deployment, following module must be enabled:
  • platform
  • nef
  • common
NEF global.envManageNF=NEF,global.envSystemName=NEF,common.configmapApplicationConfig.nrfClientType=NEF Since GUI service is an common service which defined under common module, it requires a startup parameter to show which NF should be showed under specific deployment. Same process logic applies to nrfclient service.

MetalLB Settings for Upgrade

After executing the helm upgrade command, the configured MetalLB settings may lost. User is required to update the settings manually by following the procedure in the Enabling Loadbalancer with MetalLB.