Configure NRF Details

NRF details must be defined during SCP installation using the SCP YAML file. User needs to update the NRF details in SCP YAML file.

Note:

User can configure a primary NRF and an optional secondary NRF (NRFs must have backend DB Synced).

An IPV4 address needs to be configured in case the NRF is outside the Kubernates cluster. If the NRF is inside the Kubernates cluster, the user can configure FQDN as well. If both IPV4 address and FQDN are provided then IPV4 Address will take precedence over FQDN.

Snippet of NRF details from custom_values.yaml is shown below:

Note:

The user needs to configure (or remove) apiPrefix parameter based on the APIPrefix supported (or not Supported) by NRF. Refer to SCP Configuration Parameters for more information on NRF parameters.

# NRF details for primary(Priority=0) and secondry(Priority=1) NRF. Note that these NRFs needs to be backend DB Synced.

# In case of no secondry NRF user can comment the secondary NRF details 

  nrfDetails:

    - nfType: []

      nrfManagement:

        fqdn: ocnrf1-ambassador.k1-nrf.svc.cluster.local

        port: '80'

        scheme: HTTP2

        priority: 0 # Default value is 0

        capacity: 100 # Default value is 100

        apiPrefix: USEast

        ipEndPoints:

          - ipv4Address: 10.104.121.231

            transport: TCP # Default value is TCP

            port: 80 # Default value is 80

      nrfDiscovery:

        fqdn: ocnrf1-ambassador.k1-nrf.svc.cluster.local

        port: '80'

        scheme: HTTP2

        priority: 0 # Default value is 0

        capacity: 100 # Default value is 100

        apiPrefix: USEast

        ipEndPoints:

          - ipv4Address: 10.104.121.231

            transport: TCP # Default value is TCP

            port: 80 # Default value is 80

    - nfType: []

      nrfManagement:

        fqdn: ocnrf2-ambassador.k1-nrf.svc.cluster.local

        port: '80'

        scheme: HTTP2

        priority: 1 # Default value is 0

        capacity: 100 # Default value is 100

        apiPrefix: USEast

        ipEndPoints:

          - ipv4Address: 10.106.232.232

            transport: TCP # Default value is TCP

            port: 80 # Default value is 80

      nrfDiscovery:

        fqdn: ocnrf2-ambassador.k1-nrf.svc.cluster.local

        port: '80'

        scheme: HTTP2

        priority: 0 # Default value is 0

        capacity: 100 # Default value is 100

        apiPrefix: USEast

        ipEndPoints:

          - ipv4Address: 10.106.232.232

            transport: TCP # Default value is TCP

            port: 80 # Default value is 80

Note:

The user need to update the FQDN, ipv4Address and Port of NRF to point to NRF's FQDN/IP and Port.