1 Introduction

1.1 Purpose and Scope

The purpose of this document is to highlight the changes made in Oracle Communications Cloud Native Core, Unified Data Repository (UDR) from release 23.3.x to release 23.4.2. These changes may have impact on the customer network operations and must be considered by the customer while planning the deployment.

1.2 Compatibility Matrix

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

Release 23.4.2

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

Release 23.4.1

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

Release 23.4.0

The following table lists the versions of added or updated components in release 23.4.0.

Table 1-1 Compatibility Matrix

Component Compatibility Version
CNE 23.4.x, 23.3.x, and 23.2.x
cnDBTier 23.4.x, 23.3.x, and 23.2.x
OSO 23.4.x, 23.3.x, 23.2.x, and 22.3.x
CNC Console 23.4.0
ATS 23.4.0

1.3 Common Services Load Lineup

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

Release 23.4.2

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

Table 1-2 Common Services Load Lineup

Common Service Version
Alternate Route Svc 23.4.7
App-Info 23.4.9
ATS Framework 23.4.3
Config-Server 23.4.9
Debug-tool 23.4.2
Ingress Gateway 23.4.7
Egress Gateway 23.4.7
Helm Test 23.4.2
NRF-Client 23.4.5
Perf-Info 23.4.9

Release 23.4.1

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

Table 1-3 Common Services Load Lineup

Common Service Version
Alternate Route Svc 23.4.5
App-Info 23.4.5
ATS Framework 23.4.3
Config-Server 23.4.5
Debug-tool 23.4.1
Ingress Gateway 23.4.5
Egress Gateway 23.4.5
Helm Test 23.4.1
NRF-Client 23.4.3
Perf-Info 23.4.5

Release 23.4.0

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

Table 1-4 Common Services Load Lineup

Common Service Version
Alternate Route Svc 23.4.3
App-Info 23.4.2
ATS Framework 23.4.0
Config-Server 23.4.2
Debug-tool 23.4.0
Ingress Gateway 23.4.3
Egress Gateway 23.4.3
Helm Test 23.4.0
NRF-Client 23.4.2
Perf-Info 23.4.2

1.4 Software Requirements

This section lists the added or updated software required to install UDR release 23.4.x. For more information about software requirements, see Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

Release 23.4.2

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

Release 23.4.1

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

Release 23.4.0

This section lists the updated software requirements to install Oracle Communications Cloud Native Core, Unified Data Repository (UDR).

Table 1-5 Software Requirements

Software Chart Version
Kubernetes 1.27.x
Helm 3.12.3

Table 1-6 Additional Software

Software Chart Version Required for
metallb 0.13.11 External IP

1.5 Orchestration

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

Release 23.4.2

There is no change to the orchestration in this release.

Release 23.4.1

There is no change to the orchestration in this release.

Release 23.4.0

The following table provides information about orchestration changes in release 23.4.0.

Table 1-7 Orchestration

Orchestration Changes Status Notes
Support for in-service upgrade and roll back Yes For more information about upgrade and roll back, see Supported Upgrade and Rollback Paths section.
Changes in the custom-values.yaml file Yes For more information, refer to Helm.
Changes in the resource information for custom-values.yaml file Yes For more information, refer to Resource Requirements.
Changes in the CSAR package Yes
Following changes are made in CSAR package:
  • With this release, we have one customer-specific CSAR package and generic TGZ package.
Note: For more information on specific CSAR changes, contact My Oracle Support.
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 Yes UDR supports Helm Test. For more information, see Helm Test section in Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

1.6 Resource Requirements

This section lists the added or updated resource requirements in Release 23.4.x. For more information about resource requirements, see Oracle Communications Cloud Native Core, Unified Data Repository Installation, Upgrade, and Fault Recovery Guide.

Release 23.4.2

There is no resource requirements added in this release.

Release 23.4.1

There is no resource requirements added in this release.

Release 23.4.0

The following table list the added or updated resource requirements in release 23.4.0.

Table 1-8 Resource Profile for UDR Deployment

Resource Requirement Minimum Minimum (Including side car requirement) Default Default (Including side car requirement) Performance-25K Diameter Only Performance-10K Policy Performance-25K SH and 2K SOAP
CPU 26 CPUs 48 CPUs 64 CPUs 102 CPUs 71 CPUs 136 CPUs 122 GB
Memory 26 GB 48 GB 64CPUs 102 GB 86 GB 118 GB 134 GB
Ephemeral Storage 21 GB 21 GB 38 GB 38 GB 23 GB 38 GB 53 GB

Table 1-9 Resource Profile for SLF Deployment

Resource Requirement (Includes side car requirement) Minimum Minimum (Including side car requirement) Default Default (Including side car requirement) Performance-5.5K SLF Performance-36K SLF Performance-12.1K SLF
CPU 21 CPUs 38 CPUs 46 CPUs 77 CPUs 147 CPUs 263 CPUs 111 CPUs
Memory 17 GB 34 GB 46 GB 76 GB 131 GB 159 GB 82 CPUs
Ephemeral Storage 17 GB 17 GB 29 GB 29 GB 31 GB 41 GB 26 CPUs

Table 1-10 Resource Profile for EIR Deployment

Resource Requirement (Includes side car requirement) Minimum Minimum (Including side car requirement) Default Default (Including side car requirement) Performance-10K EIR Lookup
CPU 22 CPUs 40 CPUs 47 CPUs 80 CPUs 104 CPUs
Memory 18 GB 36 GB 47 GB 79 GB 90 GB
Ephemeral Storage 18 GB 18 GB 30 GB 30 GB 37 GB
The following table shows the default resource requirements to deploy UDR:

Table 1-11 Default Resource Requirements: UDR with Aspen Service Mesh (ASM) Enabled

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU Total Memory Total Ephemeral Storage
nudr-drservice 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dr-provservice 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 GB 2 2 CPUs 4 GB 2 GB
ingressgateway-sig 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-prov 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
egressgateway 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-diameterproxy 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
diam-gateway 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-ondemandmigration 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-notify-service 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
alternate-route 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
perf-info 1 CPU 1 GB 1 GB 2 2 CPU 2 GB 2 GB
app-info 0.5 CPU 1 GB 1 GB 2 2 CPU 2 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 2 2 CPU 2 GB 2 GB
nudr-dbcr-auditor-service 2 CPUs 2 GB 1 GB 1 2 CPU 2 GB 1 GB
Total - - - - CPU Memory Ephemeral Storage
Total resources (Considering Main service containers) - - - - 56 CPUs 56 GB 31 GB
Additional Resources (Hooks/Init/Update Containers) - - - - 8 CPUs 8 GB 7 GB
Total Resources - - - - 64 CPUs 64 GB 38 GB
Total side car resources (Applicable for ASM setups) - - - - 38 CPUs 38 GB NA
Grand Total for UDR with side car requirement - - - - 102 CPUs 102 GB 38 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.
The minimum resource requirements to install UDR with ASM enabled are:

Table 1-12 Minimum Resource Requirements: UDR with Aspen Service Mesh (ASM) Enabled

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage Per Pod Replicas (As per minimum deployment) Total CPU Total Memory Total Ephemeral Storage
nudr-drservice 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-dr-provservice 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-config 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-config-server 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
ingressgateway-sig 2 CPUs 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
ingressgateway-prov 2 CPUs 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
egressgateway 2 CPUs 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-diameterproxy 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
diam-gateway 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-ondemandmigration 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-notify-service 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
alternate-route 2 CPU 1 GB 1 GB 1 2 CPU 2 GB 1 GB
perf-info 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
app-info 0.5 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
nudr-dbcr-auditor-service 1 CPUs 1 GB 1 GB 1 1 CPU 1 GB 1 GB
Total - - - - CPU Memory Ephemeral Storage
Total UDR resources (Considering default values) - - - - 20 CPUs 20 GB 16 GB
Additional Resources (Hooks/Init/Update Containers) - - - - 6 CPUs 6 GB 5 GB
Total Resources - - - - 26 CPUs 26 GB 21 GB
Total side car resources (Applicable for ASM setups) - - - - 22 CPUs 22 GB NA
Grand Total for SLF with side car - - - - 48 CPUs 48 GB 21 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.
The resources required to deploy Performance 25K SH and 2K SOAP are:

Table 1-13 Performance 25K SH and 2K SOAP

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage per pod Replicas Total CPU Total Memory Total Ephemeral Storage
nudr-diam-gateway 6 CPUs 4 GB 1 GB 3 18 CPUs 12 GB 3 GB
nudr-diameterproxy 3 CPUs 4 GB 1 GB 19 57 CPUs 76 GB 19 GB
ingressgateway-sig 2 CPU 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-prov 2 CPU 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
egressgateway 2 CPU 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-drservice 2 CPU 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dr-provservice 2 CPU 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
nudr-config-server 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
alternate-route 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
perf-info 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
app-info 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
nudr-dbcr-auditor-service 1 CPUs 1 GB 1 GB 1 1 CPU 1 GB 1 GB
Additional Resources (Hooks/Init/Update Containers)         14 CPUs 14 GB 8 GB
Total Resources         122 CPUs 134 GB 53 GB

Table 1-14 Default Resource Requirements: SLF with ASM enabled

Microservice Name CPU Per Pod Memory Per Pod Sidecar container CPU Per Pod Sidecar container Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU (Micro service + Sidecar Containers) Total Memory for the Pod (Micro service + Sidecar Containers) Total Ephemeral Storage
nudr-drservice 2 CPUs 2 GB 1 CPUs 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-dr-provservice 2 CPUs 2 GB 1 CPUs 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-config 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-sig 2 CPUs 2 GB 1 CPUs 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
ingressgateway-prov 2 CPUs 2 GB 1 CPUs 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
egressgateway 2 CPUs 2 GB 1 CPUs 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
alternate-route 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
perf-info 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
app-info 0.5 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
Total - - - - - - CPU Memory Ephemeral Storage
SLF resource Requirement - - - - - - 39 CPUs 39 GB 23 GB
Additional Resources (Hooks/Init/Update Containers) - - - - - - 8 CPUs 8 GB 7 GB
SLF Total Resources - - - - - - 47 CPUs 47 GB 30 GB
Total side car resources - - - - - - 32 CPUs 31 GB NA
Total Resources - - - - - - 79 CPUs 78 GB 30 GB
The resource requirements to install SLF with ASM enabled are:

Table 1-15 Minimum Resource Requirements: SLF with ASM Enabled

Microservice Name CPU Per Pod Memory Per Pod Sidecar container CPU Per Pod Sidecar container Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU (Micro service + Sidecar Containers) Total Memory for the Pod (Micro service + Sidecar Containers) Total Ephemeral Storage
nudr-drservice 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-dr-provservice 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-config 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-config-server 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
ingressgateway-sig 2 CPUs 1 GB 1 CPU 1 GB 1 GB 1 3 CPUs 2 GB 1 GB
ingressgateway-prov 2 CPUs 1 GB 1 CPU 1 GB 1 GB 1 3 CPUs 2 GB 1 GB
egressgateway 2 CPUs 1 GB 1 CPU 1 GB 1 GB 1 3 CPUs 2 GB 1 GB
alternate-route 2 CPU 1 GB 1 CPU 1 GB 1 GB 1 3 CPUs 2 GB 1 GB
perf-info 1 CPU 1GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
app-info 0.5 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
Total - - - - - - CPU Memory Ephemeral Storage
SLF resource Requirement - - - - - - 16 CPUs 12 GB 12 GB
Additional Resources (Hooks/Init/Update Containers) - - - - - - 6 CPUs 6 GB 6 GB
SLF Total Resources - - - - - - 22 CPUs 18 GB 18 GB
Total side car resources - - - - - - 18 CPUs 18 GB NA
Total Resources - - - - - - 40 CPUs 36 GB 18 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.
The performance based resource requirements are as follows:

Note:

This deployment can support 5.7K SLF traffic (200 Provisioning + 5500 SLF Lookup). The subscriber size on cnDBTier used for testing is 12M.

Table 1-16 Resource Requirements - Performance 5.5K for SLF

Microservice Name CPU Per Pod Memory Per Pod Sidecar container CPU Per Pod Sidecar container Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU (Micro service + Sidecar Containers) Total Memory for the Pod (Micro service + Sidecar Containers) Total Ephemeral Storage
nudr-drservice 5 CPUs 4 GB 4 CPUs 4 GB 1 GB 4 36 CPUs 32 GB 4 GB
nudr-dr-provservice 5 CPUs 4 GB 4 CPUs 4 GB 1 GB 2 18 CPUs 16 GB 2 GB
nudr-config 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-sig 6 CPUs 4 GB 4 CPUs 4 GB 1 GB 2 20 CPUs 16 GB 2 GB
ingressgateway-prov 6 CPUs 4 GB 4 CPUs 4 GB 1 GB 2 20 CPUs 16 GB 2 GB
egressgateway 2 CPUs 2 GB 2 CPUs 1 GB 1 GB 2 8 CPUs 6 GB 2 GB
alternate-route 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
perf-info 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
app-info 0.5 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
Total - - - - - - CPU Memory Ephemeral Storage
SLF resource Requirement - - - - - - 77 CPUs 63 GB 25 GB
Additional Resources (Hooks/Init/Update Containers) - - - - - - 7 CPUs 7 GB 7 GB
SLF Total Resources - - - - - - 84 CPUs 70 GB 32 GB
Total side car resources - - - - - - 65 CPUs 63 GB NA
Total Resources - - - - - - 149 CPUs 133 GB 32 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.
The performance deployment can support 36K SLF traffic + 1.26K Provisioning. The subscriber size on cnDBTier used for testing is 50M.

Table 1-17 Resource Requirements - Performance 36K for SLF

Microservice Name CPU Per Pod Memory Per Pod Sidecar container CPU Per Pod Sidecar container Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU (Micro service + Sidecar Containers) Total Memory for the Pod (Micro service + Sidecar Containers) Total Ephemeral Storage
nudr-drservice 7 CPUs 4 GB 3 CPUs 1 GB 1 GB 10 100 CPUs 50 GB 10 GB
nudr-dr-provservice 4 CPUs 4 GB 3 CPUs 1 GB 1 GB 2 14 CPUs 10 GB 2 GB
nudr-config 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-sig 6 CPUs 4 GB 3 CPUs 1 GB 1 GB 10 90 CPUs 50 GB 10 GB
ingressgateway-prov 6 CPUs 4 GB 3 CPUs 1 GB 1 GB 2 18 CPUs 10 GB 2 GB
egressgateway 2 CPUs 2 GB 2 CPUs 1 GB 1 GB 2 8 CPUs 6 GB 2 GB
alternate-route 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
perf-info 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
app-info 0.5 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
Total - - - - - - CPU Memory Ephemeral Storage
SLF resource Requirement - - - - - - 173 CPUs 119 GB 39 GB
Additional Resources (Hooks/Init/Update Containers) - - - - - - 3 CPUs 3 GB 3 GB
SLF Total Resources - - - - - - 176 CPUs 122 GB 42 GB
Total side car resources - - - - - - 89 CPUs 39 GB NA
Total Resources - - - - - - 265 CPUs 161 GB 42 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.
The performance deployment can support 12.1K SLF traffic + 1.26K Provisioning. The subscriber size on cnDBTier used for testing is 37M.

Table 1-18 Resource Requirements - Performance 12.1K for SLF

Microservice Name CPU Per Pod Memory Per Pod Sidecar container CPU Per Pod Sidecar container Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU (Micro service + Sidecar Containers) Total Memory for the Pod (Micro service + Sidecar Containers) Total Ephemeral Storage
nudr-drservice 6 CPUs 4 GB 2 CPUs 1 GB 1 GB 3 24 CPUs 15 GB 3 GB
nudr-dr-provservice 4 CPUs 4 GB 1 CPUs 1 GB 1 GB 2 12 CPUs 10GB 2 GB
nudr-config 2 CPUs 2 GB 1 CPU 1 GB 1 GB 1 3 CPUs 3 GB 1 GB
nudr-config-server 2 CPUs 2 GB 1 CPU 1 GB 1 GB 1 3CPUs 3 GB 1 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-sig 6 CPUs 4 GB 4 CPUs 1 GB 1 GB 4 40 CPUs 20 GB 4 GB
ingressgateway-prov 4 CPUs 4 GB 2 CPUs 1 GB 1 GB 2 12 CPUs 10 GB 2 GB
egressgateway 1 CPUs 1 GB 1 CPUs 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
alternate-route 2 CPUs 2 GB 1 CPU 1 GB 1 GB 2 6 CPUs 6 GB 2 GB
perf-info 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
app-info 1 CPU 1 GB 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 CPU 1 GB 1 GB 1 2 CPUs 2 GB 1 GB
Total - - - - - - CPU Memory Ephemeral Storage
SLF resource Requirement - - - - - - 73 CPUs 57 GB 24 GB
Additional Resources (Hooks/Init/Update Containers) - - - - - - 3 CPUs 3 GB 3 GB
SLF Total Resources - - - - - - 76 CPUs 60 GB 27 GB
Total side car resources - - - - - - 41 CPUs 24 GB NA
Total Resources - - - - - - 117 CPUs 84 GB 27 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.

Table 1-19 Default Resource Requirements: EIR

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU Total Memory for the Pod Total Ephemeral Storage
nudr-drservice 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-dr-provservice 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-sig 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
ingressgateway-prov 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
egressgateway 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
alternate-route 2 CPUs 2 GB 1 GB 2 4 CPUs 2 GB 2 GB
perf-info 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
app-info 0.5 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
Total - - - - CPU Memory Ephemeral Storage
EIR resource Requirement - - - - 39 CPUs 39 GB 23 GB
Additional Resources (Hooks/Init/Update Containers) - - - - 8 CPUs 8 GB 7 GB
EIR Total Resources - - - - 47 CPUs 47 GB 30 GB
Total side car resources, if installed with ASM - - - - 33 CPUs 32 GB NA
Total Resources - - - - 80 CPUs 79 GB 30 GB

Table 1-20 Minimum Resource Requirements: EIR

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage Per Pod Replicas (As per minimum deployment) Total CPU Total Memory for the Pod Total Ephemeral Storage
nudr-drservice 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-dr-provservice 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-config 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-config-server 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
ingressgateway-sig 2 CPUs 1 GB 1 GB 1 2 CPUs 1 GB 1 GB
ingressgateway-prov 2 CPUs 1 GB 1 GB 1 2 CPUs 1 GB 1 GB
egressgateway 2 CPUs 1 GB 1 GB 1 2 CPUs 1 GB 1 GB
alternate-route 2 CPU 1 GB 1 GB 1 2 CPUs 1 GB 1 GB
perf-info 1 CPU 1GB 1 GB 1 1 CPUs 1 GB 1 GB
app-info 0.5 CPU 1 GB 1 GB 1 1 CPUs 1 GB 1 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
Total - - - - CPU Memory Ephemeral Storage
EIR resource Requirement - - - - 16 CPUs 12 GB 12 GB
Additional Resources (Hooks/Init/Update Containers) - - - - 6 CPUs 6 GB 6 GB
EIR Total Resources - - - - 22 CPUs 18 GB 18 GB
Total side car resources, if installed with ASM - - - - 18 CPUs 18 GB NA
Total Resources - - - - 40 CPUs 36 GB 18 GB
The performance based resource requirements are as follows:

Note:

This deployment can support 10k EIR EIC traffic. The subscriber size on cnDBTier used for testing is 300k.

Table 1-21 Resource Requirements - Performance 10K for EIR

Microservice Name CPU Per Pod Memory Per Pod Ephemeral Storage Per Pod Replicas (As per default deployment) Total CPU Total Memory for the Pod Total Ephemeral Storage
nudr-drservice 4 CPUs 4 GB 1 GB 6 24 CPUs 24 GB 6 GB
nudr-dr-provservice 4 CPUs 4 GB 1 GB 2 8 CPUs 8 GB 2 GB
nudr-config 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-config-server 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
nudr-nrf-client-nfmanagement 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
ingressgateway-sig 6 CPUs 4 GB 1 GB 5 30 CPUs 20 GB 5 GB
ingressgateway-prov 6 CPUs 4 GB 1 GB 2 12 CPUs 8 GB 2 GB
egressgateway 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
alternate-route 2 CPUs 2 GB 1 GB 2 4 CPUs 4 GB 2 GB
perf-info 1 CPU 1 GB 1 GB 2 2 CPUs 2 GB 1 GB
app-info 0.5 CPU 1 GB 1 GB 2 2 CPUs 2 GB 2 GB
nudr-dbcr-auditor-service 1 CPU 1 GB 1 GB 1 1 CPU 1 GB 1 GB
Total - - - - CPU Memory Ephemeral Storage
EIR resource Requirement - - - - 97 CPUs 83 GB 30 GB
Additional Resources (Hooks/Init/Update Containers) - - - - 7 CPUs 7 GB 7 GB
Total Resources - - - - 104 CPUs 90 GB 37 GB

Note:

If the debug tool is enabled, then the additional resource requirements are 1 CPU, 2GB RAM, and 4G ephemeral storage for each pod.