UDM Deployment

This procedure describes the steps to deploy UDM on CNE. The below steps need to be executed from a server which has access to Kubectl and helm commands.

Table 3-4 UDM Deployment

Step No.#	Procedure	Description
1	Search helm chart	Execute the following command to check the version of the helm chart installation. This step is required ocudm helm charts are part of some helm repository. helm search <chart_name> Note: chart_name can be obtained from Chart.yaml file in ocudm helm charts shared as part of the package.
2	Prepare custom_values.yaml file	Prepare a custom_values.yaml file with the required parameter information. Refer to Configuration Parameter for more information on parameters. You can also download sample ocudm_values.yaml file from OHC.
3	Deploy UDM using HELM repository	Execute the following command: helm install <helm-repo>/chart_name -f <custom_values.yaml> --name <deployment_name> --namespace <namespace_name> --version <helm_version> Where: helm-repo: repository name where the helm images, charts are stored custom_values: helm configuration file which needs to be updated based on the deployment site requirement deployment_name and namespace_name: depends on customer configuration. For example: helm install ocudm-helm-repo/ocudm -f <custom values.yaml> --name ocudm --namespace udmsvc --version <helm version>
4	Deploy UDM using extracted HELM charts	Execute the following command: helm install -f <custom values.yaml> --name ocudm --namespace <namespace> <chartpath>./<chart>.tgz
5	Check repo status	Execute helm status <deployment_name> to check the deployment status.
6	Check svc status	Check if all the services are deployed and running: kubectl -n <namespace_name> get services
7	Check pod status	Check if all the pods are up and running: kubectl -n <namespace_name> get pods Check OCUDM Pod Details section given below for the pod details.

OCUDM Pod Details

The OCUDM Pod details are as follows:

kubectl get pods -n myudm
NAME                                                 READY   		STATUS    RESTARTS   AGE
ocudm-ausfueauthenticator-5745c4c594-4ttnz            1/1      Running   0          3d2h
ocudm-endpoint-5f9b49689c-g4x2r                       1/1      Running   0          3d2h
ocudm-endpoint-5f9b49689c-gtw24                       1/1      Running   0          3d2h
ocudm-nudm-nrf-client-service-d65bf7b5b-s7dzx         1/1      Running   0          3d2h
ocudm-nudm-sdm-notify-service-6459c7c8cf-hph7d        1/1      Running   0          3d2h
ocudm-nudm-sdm-service-df485d6d-qtfgm                 1/1      Running   0          3d2h
ocudm-nudm-ue-auth-service-b66886d84-9p79t            1/1      Running   0          3d2h
ocudm-nudm-uecm-service-c58c5d68c-7tbqz               1/1      Running   0          3d2h                                                                                         
ocudm-perf-info-5f6b8f9856-kb5gj                      1/1      Running   0          3d2h