1. Network Repository Function (NRF) Cloud Native Installation and Upgrade Guide
  2. Deployment of OCNRF in Cloud Native Environment

6 Deployment of OCNRF in Cloud Native Environment

This chapter contains information about the OCNRF Deployment in Cloud Native Environment.

Table 6-1 OCNRF Deployment

Step # Procedure Description

1

Create customized ocnrf-custom-values-1.5.1.yaml file Create the customized ocnrf-custom-values-1.5.1.yaml with the required input parameters.

To configure the parameters, see section OCNRF Configuration.

or,

The ocnrf-custom-values-1.5.1.yaml template can be downloaded from OHC.

Download the Network Repository Function (NRF) Custom Template. Unzip the ocnrf-custom-configTemplates-1.5.1.0.0.zip to get ocnrf-custom-values-1.5.1.yaml file.

2

Go to the extracted OCNRF package

Go to the extracted OCNRF package as explained in OCNRF Installation Prerequisites:

cd ocnrf-pkg-1.5.1.0.0

3

Deploy OCNRF Execute the following command:

helm install ocnrf/ --name <helm-release> --namespace <k8s namespace> -f <ocnrf_customized_values.yaml>

For example: helm install ocnrf/ --name ocnrf --namespace ocnrf -f ocnrf-custom-values-1.5.1.yaml

4

Check status of the deployment Execute the following command:

helm status <helm-release>

For example: helm status ocnrf

5

Check status of the services Execute the following command:

kubectl -n <k8s namespace> get services

For example:

kubectl -n ocnrf get services

Note: If metallb is used, EXTERNAL-IP is assigned to <helm release name>-endpoint. ocnrf is the helm release name. 

NAME                     TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
ocnrf-egressgateway      ClusterIP      10.233.1.61     <none>        8080/TCP,5701/TCP   30h
ocnrf-ingressgateway     LoadBalancer   10.233.52.194   <pending>     80:31776/TCP        30h
ocnrf-nfaccesstoken      ClusterIP      10.233.53.115   <none>        8080/TCP            30h
ocnrf-nfdiscovery        ClusterIP      10.233.21.28    <none>        8080/TCP            30h
ocnrf-nfregistration     ClusterIP      10.233.4.140    <none>        8080/TCP            30h
ocnrf-nfsubscription     ClusterIP      10.233.44.98    <none>        8080/TCP            30h
ocnrf-nrfauditor         ClusterIP      10.233.1.71     <none>        8080/TCP            30h
ocnrf-nrfconfiguration   LoadBalancer   10.233.40.230   <pending>     8080:30076/TCP      30h

6

Check status of the pods Execute the following command:

kubectl get pods -n <k8s namespace>

Status column of all the pods should be 'Running'.

Ready column of all the pods should be n/n, where n is number of containers in the pod.

For example:

kubectl get pods -n ocnrf 

NAME                                      READY   STATUS    RESTARTS   AGE
ocnrf-egressgateway-d6567bbdb-9jrsx       2/2     Running   0          30h
ocnrf-egressgateway-d6567bbdb-ntn2v       2/2     Running   0          30h
ocnrf-ingressgateway-754d645984-h9vzq     2/2     Running   0          30h
ocnrf-ingressgateway-754d645984-njz4w     2/2     Running   0          30h
ocnrf-nfaccesstoken-59fb96494c-k8w9p      2/2     Running   0          30h
ocnrf-nfaccesstoken-49fb96494c-k8w9q      2/2     Running   0          30h
ocnrf-nfdiscovery-84965d4fb9-rjxg2        1/1     Running   0          30h
ocnrf-nfdiscovery-94965d4fb9-rjxg3        1/1     Running   0          30h
ocnrf-nfregistration-64f4d8f5d5-6q92j     1/1     Running   0          30h
ocnrf-nfregistration-44f4d8f5d5-6q92i     1/1     Running   0          30h
ocnrf-nfsubscription-5b6db965b9-gcvpf     1/1     Running   0          30h
ocnrf-nfsubscription-4b6db965b9-gcvpe     1/1     Running   0          30h
ocnrf-nrfauditor-67b676dd87-xktbm         1/1     Running   0          30h
ocnrf-nrfconfiguration-678fddc5f5-c5htj   1/1     Running   0          30h