Updating nrf Client Service Related configmap

User may have to update nrf client service related configmap. Following are few scenarios:

• Currently deployed BSF uses updated configmap to register BSF itself to NRF service.
• Client gets BSF related FQDN, IPv4, or IPv6 address from NRF service and send request to specific service under BSF with that FQDN, IPv4 or IPv6 address. The request reaches to API Gateway service under BSF deployment.
• The API Gateway service under BSF would parse coming request, then distributes that request to specific service per request URL and forward response from upstream service to client.

The nrf client configmap establish connection between NRF and BSF, in order to register BSF to NRF services and hence it is mandatory to update configmap to use correct nrf service URL and apply some extra settings.

Note:

If no NRF deployed under current kubernetes cluster, then ignore the following settings under this section as there is no need for BSF to register itself to NRF service. The only way to invoke BSF services is to get API service URL manually then send request to it directly.

Before updating nrf client service, perform the following:

• Get nrf Service URL
• Get BSF Profile

To update nrf client service:

1. Run the following command and get config map item, <BSF-NAME>-application-config:

   kubectl get configmap -n < BSF-Namespace>

2. Run the following command and then navigate to vim editor with config map content displayed

   kubectl edit configmap <BSF-NAME>-application-config -n <BSF-Namespace>

3. Update nrfApiRoot to actual deployed nrf service URL. For example, nrfApiRoot=http://ocnrf-endpoint.nrf1-1:80. See Get nrf Service URL to get actual nrf service URL.

   At least one of the address parameters such as fqdn, ipv4address or ipv6adress should be populated in the NF Profile under configmap definition. NF Profile here indicates the entrance of current deployed BSF which means it is the API Gateway service URL(FQDN), API Gateway service IP V4 address or IP V6 address.

   appProfiles=[{"nfInstanceId": "fe7d882b-0541-4c7d-ab84-c6d70b1b0123","nfType": "PCF","nfStatus": "REGISTERED","plmn": null,"nsiList": null, "fqdn": null,"interPlmnFqdn": null, "ipv4Addresses": null,"ipv6Addresses": null.......

   It is recommended to update the fqdn value while keeping ipv4Addresses and ipv6Addresses as it is.

   For example, consider ocbsf-api-gateway.bsf1-1:80 for fqdn value. Following result displays:

   appProfiles=[{"nfInstanceId": "fe7d882b-0541-4c7d-ab84-c6d70b1b0123","nfType": "PCF","nfStatus": "REGISTERED","plmn": null,"nsiList": null, "fqdn": "ocbsf-api-gateway.bsf1-1:80","interPlmnFqdn": null, "ipv4Addresses": null,"ipv6Addresses": null.......

   Refer to Get BSF Profile to get actual fqdn value.

4. Set

   "ipEndPoints":[{"ipv4Address":"ocpm-staging-bsf-2-api-gateway.ocpm-staging-bsf-2.svc","ipv6Address":null,"transport":"TCP","port":5903}] to "ipEndPoints": null

5. Quit vim edit mode and save the changes. Wait for a while to verify whether BSF had been registered to NRF or not.