F NRF Recommended Features
This section details the recommended features that are to be enabled mandatorily during the deployment of NRF at the production-level.
Table F-1 NRF Recommended Features
| Feature Name | Sub Features | Overview |
|---|---|---|
| Limiting Number of NFProfiles in NFDiscover Response | NA | This feature controls the count of NFProfiles in the
NFDiscover service operation response.
For more information, see Limiting Number of NFProfiles in NFDiscover Response. |
| Network Policies | NA | This feature allows to specify how a pod is allowed to
communicate with various network entities.
For more information, see Network Policies. Note: Should be enabled. |
| Pod Protection Support for NRF Subscription Microservice | NA | NRF
Subscription microservice is responsible for the NfStatusSubscribe,
NfStatusUnsubscribe, and NfStatusNotify service operations. During
processing of these service operations, Subscription microservice may
get into congested or overload conditions. This feature protects the
Subscription microservice from overload situations and maintains the
overall health of the microservice.
For more information, see Pod Protection Support for NRF Subscription Microservice. |
| Pre and Post Install/Upgrade Validations | NRF Infrastructure Validation | This feature helps in validating the infrastructure
specific details such as NRF version, Kubernetes version, cnDBTier
version, replication status, and alerts during NRF install and upgrade
procedure.
For more information, see NRF Infrastructure Validation. |
| Overload Control Based on Percentage Discards | Pod Level Traffic Rejections | NRF supports overload control to protect the nfregistration,
nfdiscovery, nfsubscription, and nfaccesstoken services from overload
situations and maintain the overall health of the services. This feature
helps you to protect, mitigate, avoid entering into an overload
condition, detect overload conditions, and take necessary actions to
recover from overload.
For more information, see Overload Control. |
| Subscription Limit | NA | NRF
restricts the maximum number of allowed subscriptions to avoid the
overload condition at NRF subscription microservice. NRF regulates the total
number of allowed subscriptions using a configurable Global Subscription
Limit. In case of georedundant NRFs, the limit is applied across all of the
mated sites.
For more information, see Subscription Limit. |
| Error Log Messages Enhancements | NA | NRF adds additional information to the existing
ERROR log messages. This additional information can
provide more details about the error which can help to identify the
problem details, error generating entity, and subscriber information.
For more information, see Error Log Messages Enhancement. |
| User-Agent Header for Outgoing Requests | NA | NRF
supports the addition of User-Agent header for outgoing messages such as
NFStatusNotify and SLF query requests. If the User-Agent header value is
configured, then NRF adds the User-Agent header with the configured value to the
mentioned outgoing messages.
For more information, see User-Agent Header for Outgoing Requests. |
| NRF Georedundancy | NA | NRF supports georedundancy to ensure high availability and
redundancy. It offers a two, three, or four-sites georedundancy to
ensure service availability when one of the NRF site is down. When
NRF is
deployed as georedundant site, all the sites work in an active state and
the same data is available at all the sites.
For more information, see NRF Georedundancy. Note: If the Georedundancy feature is enabled, NRF Last Known Response feature must be enabled. NRF Last Known Response: When NRF detects that the replication channel with its georedundant NRF(s) is down, it stops considering the NFs registered in the georedundant NRF(s) for any service operations. For more information, see NRF Last Known Response. |
| Controlled Shutdown of NRF | NA | NRF
supports isolating an NRF from the current network at a particular site. This
isolation helps to perform any maintenance activities or recovery
procedures as required without uninstalling the NRF at the particular
site.
For more information, see Controlled Shutdown of NRF . |
| Egress Gateway Pod Throttling | NA | With this feature, each Egress Gateway pod monitors its
incoming traffic. If the traffic exceeds the maximum defined capacity,
the excess traffic is not processed and gets rejected. The traffic
capacity is defined at each pod and applied to all the incoming requests
irrespective of the message type.
For more information, see Egress Gateway Pod Throttling. |
| Ingress Gateway Pod Protection Using Rate Limiting | NA | With this feature, the Ingress Gateway pods are protected
by restricting the pods to process only a defined number of requests.
The Ingress Gateway pods calculate the rate of the incoming requests and
evaluate if it has breached the defined threshold. If breached, the pods
reject the additional requests with the defined error code. If the rate
of incoming requests has not breached the defined threshold, the pod
allows the requests for further processing.
For more information, see Ingress Gateway Pod Protection Using Rate Limiting. |