1 Introduction

The purpose of this document is to highlight the changes made in NEF from release 24.1.x to release 24.2.x. These changes may have an impact on the customer network operations and must be considered by the customer while planning the deployment.

1.1 Compatibility Matrix

This section lists the versions of added or updated components in release 24.2.x. To know the list of all the supported versions, see Oracle Communications Cloud Native Core Release Notes.

Release 24.2.2

There is no change in the compatible matrix for this release.

Release 24.2.1

There is no change in the compatible matrix for this release.

Release 24.2.0

The following table lists the versions of added or updated components in this release:

Table 1-1 Compatibility Matrix

Component Compatible Versions
ATS 24.2.x
cnDBTier 24.2.x, 24.1.x, 23.4.x
CNE 24.2.x, 24.1.x, 23.4.x
OCI Adaptor 24.2.x

1.2 Common Services Load Lineup

This section lists the versions of added or updated common services in release 24.2.x. To know the list of all the supported versions, see Oracle Communications Cloud Native Core Release Notes.

Release 24.2.2

There is no change in the common services load lineup in this release.

Release 24.2.1

The following table lists the versions of added or updated common services in release 24.2.1.

Table 1-2 Common Services Load Lineup

Common Service Version
App-Info 24.2.15
ATS Framework 24.2.2
Common-Config-Hook 24.2.15
Config-Server 24.2.15
Configuration Update Service 24.2.15
Configuration INIT Service 24.2.15
Debug-tool 24.2.6
Egress Gateway 24.2.15
Helm Test 24.2.5
Ingress Gateway 24.2.15
NRF-Client 24.2.8
Perf-Info 24.2.15

Release 24.2.0

The following table lists the versions of added or updated common services in this release:

Table 1-3 Common Services Load Lineup

Common Service Version
App-Info 24.2.1
ATS Framework 24.2.0
Common-Config-Hook 24.2.4
Config-Server 24.2.1
Configuration Update Service 24.2.4
Configuration INIT Service 24.2.4
Debug-tool 24.2.1
Egress Gateway 24.2.4
Helm Test 24.2.1
Ingress Gateway 24.2.4
NRF-Client 24.2.1
Perf-Info 24.2.1

1.3 Software Requirements

This section lists the added or updated software required to install NEF release 24.2.x. For more information about software requirements, see Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.

Release 24.2.2

There is no change in the software requirements for this release.

Release 24.2.1

There is no change in the software requirements for this release.

Release 24.2.0

The following table lists the versions of added or updated software required to install this release:

Table 1-4 Software Requirements

Software Versions
Helm 3.13.2
Kubernetes 1.29.x, 1.28.x, 1.27.x
The following table lists the versions of additional software along with the usage:

Table 1-5 Additional Software

Software Version Purpose
Calico 3.26.4 Logging
cert-manager 1.12.4 Logging
containerd 1.7.13 Logging
Grafana 9.5.3 Metrics
Istio 1.18.2 Logging
Jaeger 1.52.0 Logging
Kyverno 1.9.0 Logging
MetalLb 0.14.4 Logging
Prometheus 2.51.1 Metrics
Prometheus Operator 0.72.0 Metrics

1.4 Orchestration

This section provides information about orchestration changes in release 24.2.x.

Release 24.2.2

There is no change to the orchestration in this release.

Release 24.2.1

There is no change to the orchestration in this release.

Release 24.2.0

The following table provides information about orchestration changes in this release:

Table 1-6 Orchestration

Orchestration Changes Status Notes
Support for in-service upgrade and roll back Yes For information about upgrade and roll back, see Supported Upgrade and Rollback Paths.
Changes in the custom-values.yaml file Yes NEF architecture supports the following custom values files:
  • ocnef-custom-values.yaml
  • occapif-custom-values.yaml
For information about the custom-values.yaml file, see Helm.
Changes in the resource information for ocnef-custom-values.yaml and occapif-custom-values.yaml files Yes For information about changes in the resource requirements, see Resource Requirements.
Changes in the CSAR package No No CSAR package changes.
Changes in Role-Based Access Control (RBAC) policy No No new RBAC policies are added.
Changes in Life Cycle Management (LCM) Operations No No new LCM operations are added.
Helm Test Support No For information about Helm test, see the "Performing Helm Test" section in Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.

1.5 Resource Requirements

This section lists the added or updated resource requirements in release 24.2.x. For more information about resource requirements, see Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.

Note:

Changes in the resource requirements are highlighted in bold.

Release 24.2.2

There is no resource requirements added in this release.

Release 24.2.1

There is no resource requirements added in this release.

Release 24.2.0

The following table lists the added or updated resource requirements in this release:

Table 1-7 Resource Requirements for NEF Services

Microservice Name CPU Request and limit per POD (A) Memory Request and limit per POD (B) Scaling Criteria CPU Usage % Default POD Count (C) Maximum POD count with scaling (D) Minimum CPU Total for Default PODs (A*C) Minimum Memory Total for Default PODs (B*C) Maximum CPU Total for all PODs (with full scaling and surge) (A*D) Maximum Memory Total for all PODs (with full scaling and surge) (B*D) CPU Request and limit for Debug Container (Optional) Memory Request and limit for Debug Container (Optional)
APD Manager 4 4Gi 70 2 2 8 8Gi 8 8Gi 1 2Gi
API Router 4 4Gi 70 2 2 8 8Gi 8 8Gi 1 2Gi
External Egress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
External Ingress Gateway 4 4Gi 70 2 5 8 8Gi 20 520Gi 1 2Gi
5GC Egress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
5GC Ingress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
Common Config Hook 1 1Gi 1 1 1 1 1Gi 1 1Gi 1 2Gi
ME Service 4 4Gi 70 2 12 8 8Gi 48 48Gi 1 2Gi
QoS Service 4 4Gi 70 2 12 8 8Gi 48 48Gi 1 2Gi
5GC Agent 4 4Gi 70 2 12 8 8Gi 48 48Gi 1 2Gi
CCF Client 2 2Gi 70 2 3 4 4Gi 6 6Gi 1 2Gi
Expiry Auditor 4 4Gi 70 2 3 8 8Gi 12 12Gi 1 2Gi
Perf-Info 1 1Gi 1 1 1 1 1Gi 1 1Gi 1 2Gi
App-Info 1 1Gi 1 1 1 1 1Gi 1 1Gi 1 2Gi
Config-Server 1 1Gi 1 1 1 1 1Gi 1 1Gi 1 2Gi
NRF Client 1 1Gi 1 1 1 1 1Gi 1 1Gi 1 2Gi
Traffic Influence 4 4Gi 70 2 12 8 8Gi 48 48Gi 1 2Gi
Diameter Gateway 4 4Gi 70 2 2 8 8Gi 8 8Gi 1 2Gi
Device Trigger 1 1Gi 70 1 1 1 1Gi 1 1Gi 1 1Gi
Pool Manager 4 4Gi 70 1 1 4 4Gi 4 4Gi 1 1Gi
MSISDNless MO SMS 4 4Gi 70 1 12 4 4Gi 4 4Gi 4 4Gi
Console Data Service 4 4Gi 70 1 12 4 4Gi 4 4Gi 4 4Gi

Note:

The debug container resources are optional. If you are using the debug container, then the CPU Request and Limit for Debug Container and Memory Request and Limit for Debug Container values must be included to the minimum and maximum resources for NEF services.

Table 1-8 Resource Requirements for CAPIF Services

Microservice Name CPU Request and limit per POD (A) Memory Request and limit per POD (B) Scaling Criteria CPU Usage % Default POD Count (C) Maximum POD count with scaling (D) Minimum CPU Total for Default PODs (A*C) Minimum Memory Total for Default PODs (B*C) Maximum CPU Total for all PODs (with full scaling and surge) (A*D) Maximum Memory Total for all PODs (with full scaling and surge) (B*D) CPU Request and limit for Debug Container (Optional) Memory Request and limit for Debug Container (Optional)
API Manager 4 4Gi 70 2 3 8 8Gi 12 12Gi 1 2Gi
AF Manager 4 4Gi 70 2 3 8 8Gi 12 12Gi 1 2Gi
Event Manager 4 4Gi 70 2 2 8 8Gi 8 8Gi 1 2Gi
External Ingress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
External Egress Gateway 4 4Gi 70 2 5 8 8Gi 10 20Gi 1 2Gi
Network Ingress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
Network Egress Gateway 4 4Gi 70 2 5 8 8Gi 20 20Gi 1 2Gi
Console Data Service 4 4Gi 70 1 12 4 4Gi 4 4Gi 4 4Gi

Note:

The debug container resources are optional. If you are using the debug container, then the CPU Request and Limit for Debug Container and Memory Request and Limit for Debug Container values must be included to the minimum and maximum resources for CAPIF services.