What's New in This Guide
This section introduces the documentation updates for release 25.2.2xx.
Release 25.2.201- G46998-02, April 2026
Upgrade, Rollback, and Uninstall Updates
Added a note to indicate that an additional step is required while performing an
upgrade from 25.1.2xx to 25.2.2xx in the following sections:
Release 25.2.201- G46998-01, April 2026
General Updates
- Updated the Table 1-1 table with the release information in the Oracle Error Correction Policy section.
- Updated the release number to 25.2.201 throughout the document.
- Updated the preinstalled and additional software versions in the Software Requirements section.
- Updated the image tag details in the following sections:
- Updated the Pushing the Images to Customer Docker Registry, Pushing the NRF Images to OCI Docker Registry, and NRF Customization sections for replacing the
ocnrf_configuration_openapi_25.2.201.yamlwithocnrf_configuration_openapi_25.2.201.jsonas openAPI specification support is transitioned from YAML to JSON. - Added Customization of OpenAPI JSON appendix for updating the OpenAPI
serversURLs and select the appropriate server for the required API group. - Updated the Alert Configuration section by removing the content related to updating NRF alerts for CNE 1.8.x and earlier versions and adding content to update NRF alerts for OSO releases.
- Added NRF Traffic IP Flow appendix to include the port details for NRF traffic.
Installation Updates
- Updated the versions for the following
appValidateparameters in the Global Parameters section:global.appValidate.minViablePathto 25.1.200global.appValidate.minKubernetesVersionto 1.32.0global.appValidate.minDbTierVersionto 25.1.200
- Removed the
ocnrf_dashboard_promha_25.2.201.yamlfile from the CSAR package in the following sections as the current dashboard supports configuring both promha and OSO. - Added a note in the CNC Console Requirements section to update cnDBTier resources before installing or upgrading the CNC Console.
- Updated the cnDBTier parameters table in the cnDBTier Requirement section:
- Removed the
global.additionalndbconfigurations.appmysqld.ndb_event buffer_max_allocparameter because the recommended value is now the default value. - Modified the recommended value of
global.additionalndbconfigurations.ndb.MaxNoOfOrderedIndexesparameter from 3630 to 5120. - Removed the
db-replicationsvc.initiatebackupBeforeGeoRecoveryRestoreparameter and replaced it with theglobal.geoReplicationRecovery.backupFailedSite.enableparameter. - Modified the default value of the
global.api.binlogpurgetimerfrom NA to 600s and changed the status from Added to Modified. - Added the following parameters:
global.additionalndbconfigurations.ndb.MaxNoOfAttributesglobal.additionalndbconfigurations.ndb.MaxNoOfUniqueHashIndexesglobal.additionalndbconfigurations.mgm.TotalSendBufferMemoryglobal.additionalndbconfigurations.ndb.TotalSendBufferMemoryglobal.additionalndbconfigurations.ndb.MaxNoOfTablesglobal.additionalndbconfigurations.api.TotalSendBufferMemoryglobal.additionalndbconfigurations.tcpemptyapi.TotalSendBufferMemoryglobal.additionalndbconfigurations.tcpemptyapi.SendBufferMemoryglobal.additionalndbconfigurations.ndb.ndbdisksizeglobal.additionalndbconfigurations.ndb.ndbbackupdisksizeglobal.additionalndbconfigurations.ndb.datamemoryglobal.additionalndbconfigurations.ndb.retainbackupnoglobal.additionalndbconfigurations.api.ndbdisksizeglobal.ndb.delayPerDataPod
- Removed the
- Modified the values of the minimum and maximum CPU or Pod values for
the following cnDBTier resources in the cnDBTier Services section:
- Backup Manager Service (db-backup-manager-svc)
- Replication Service - Other
- Modified the minimum memory/Pod value for the
MGMT (ndbmgmd)service from 8 to 10 in the cnDBTier Services section. - Modified the PVC1 size for the
SQL(ndbmysqld)service from 13 to 90 in the cnDBTier Services section. - Modified the minimum ephemeral storage for all the cnDBTier services and cnDBTier Sidecar resources from 90 to 200 in the cnDBTier Services and cnDBTier Sidecars sections.
- Modified the maximum value of the ephemeral storage for the
db-executor-svcsidecar container from 1 to 2 in the cnDBTier Sidecars section. - Modified the minimum and maximum CPU/Pod value for the
db-infra-monitor-svcsidecar container from 0.1 to 0.2 in the cnDBTier Sidecars section. - Added a note in the Service Mesh Sidecar section to highlight the automatic annotation injection for the sidecar.
- Modified the default values of the following parameters from
IfNotPresentto*imagePullPolicy:ingress-gateway.global.debugTools.pullPolicyin the Ingress Gateway Microservice section.egress-gateway.global.debugTools.pullPolicyin the Egress Gateway Microservice section.alternate-route.global.debugTools.pullPolicyin the Alternate Route Microservice (alternate-route) section.appinfo.global.debugTools.pullPolicyin the App Info Microservice (appinfo) section.perf-info.global.debugTools.pullPolicyin the Perf Info Microservice (perf-info) section.
- Modified the default values of the following parameters:
global.defaultReplicationStatusOnErrorfrom DOWN to UP in the Global Parameters.global.overrideReplicationCheckfrom false to true in the Global Parameters section.egress-gateway.podLevelMessageThrottling.enabledfrom true to false in the Egress Gateway Microservice section.egress-gateway.maxReplicasfrom 19 to 36 in the Egress Gateway Microservice section.ingress-gateway.maxReplicasfrom 27 to 36 in the Ingress Gateway Microservice section.nfdiscovery.maxReplicasfrom 60 to 51 in the NF Discovery Microservice (nfdiscovery) section.
- Modified the description of the
defaultReplicationStatusOnErrorparameter in the Global Parameters and App Info Microservice (appinfo) sections. - Modified the description of the
egress-gateway.podLevelMessageThrottling.enabledparameter in the Egress Gateway Microservice section. - Modified the description of the
overrideReplicationCheckparameter in the following sections: - Added the following parameters in the Egress Gateway Microservice section:
egress-gateway.tlsVersionSupportForKubeApiServer.enabledegress-gateway.tlsVersionSupportForKubeApiServer.kubeApiServerTlsVersionegress-gateway.tlsVersionSupportForKubeApiServer.cipherSuitesegress-gateway.addDestHostToHttpReqMetricegress-gateway.addDestHostToJettyStatMetricegress-gateway.addDestHostToMalformedHeaderContentMetricegress-gateway.addDestinationHostToResponseMetricegress-gateway.addErrReasonToConnectionFailureMetricegress-gateway.addErrorReasonToResponseMetricegress-gateway.addHostToConnectionFailureMetricegress-gateway.addHostToIncomingConnectionsMetricegress-gateway.addHostToIncomingIpTypeMetricegress-gateway.addHostToOutgoingConnectionsMetricegress-gateway.addHostToOutgoingIpTypeMetricegress-gateway.addHostToOutgoingTlsConnectionsMetricegress-gateway.addPortToConnectionFailureMetric
- Added the following parameters in the Ingress Gateway Microservice section:
ingress-gateway.ports.actuatorPortingress-gateway.ports.actuatorPortNameingress-gateway.ports.containerPortingress-gateway.ports.containerPortNameingress-gateway.ports.containersslPortingress-gateway.ports.containersslPortNameingress-gateway.ports.containerHttp1Portingress-gateway.ports.containerHttp1PortNameingress-gateway.tlsVersionSupportForKubeApiServer.kubeApiServerTlsVersioningress-gateway.tlsVersionSupportForKubeApiServer.enabledingress-gateway.tlsVersionSupportForKubeApiServer.cipherSuitesingress-gateway.addHostToOutgoingConnectionsMetricingress-gateway.addHostToIncomingTlsConnectionsMetricingress-gateway.addHostToIncomingIpTypeMetricingress-gateway.addHostToIncomingConnectionsMetricingress-gateway.addErrorReasonToConnectionFailureMetricingress-gateway.addErrReasonToHttpRespMetricingress-gateway.addDestHostToUserAgentConsumerNfTypeMetricingress-gateway.addDestHostToJettyStatMetricingress-gateway.addDestHostToHttpRespMetricingress-gateway.addDestHostToHttpReqMetricingress-gateway.addBackendSvcToOutgoingIpTypeMetricingress-gateway.intraNfService.customExtension.labelsingress-gateway.intraNfService.customExtension.annotations
- Removed the
nfregistration.jetty.dnsRefreshDelayparameter from the NF Registration Microservice (nfregistration) section because this is handled bynfregistration.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NF Registration Microservice (nfregistration) section:
nfregistration.serviceDiscovery.cipherSuitesnfregistration.serviceDiscovery.kubeApiServerTlsVersionnfregistration.serviceDiscovery.ipConnectFailureThresholdnfregistration.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenfregistration.serviceDiscovery.fqdnInMetricsEnablednfregistration.serviceDiscovery.refreshDelaynfregistration.serviceDiscovery.timeoutnfregistration.jetty.commonCpJcMaxPayloadSizeInKBnfregistration.jetty.maxRequestsHeaderSize
- Renamed the parameter name from
nfregistration.maxAttemptstonfregistration.maxDatabaseAttemptsin the NF Registration Microservice (nfregistration) section. - Modified the default values of the following parameters in the
NF Registration Microservice (nfregistration)
section:
nfregistration.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/liveness.nfregistration.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readiness.nfregistration.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health.nfregistration.global.hikariPoolSizefrom 10 to 20.
- Removed the
nfsubscription.maxInMemorySizeparameter from the NF Subscription Microservice (nfsubscription) section because this is handled bynfsubscription.jetty.commonCpJcMaxPayloadSizeInKBparameter. - Removed the
nfsubscription.jetty.dnsRefreshDelayparameter from the NF Subscription Microservice (nfsubscription) section because this is handled bynfsubscription.serviceDiscovery.refreshDelayparameter. - Added the following parameters in theNF Subscription Microservice (nfsubscription) section :
nfsubscription.serviceDiscovery.cipherSuitesnfsubscription.serviceDiscovery.kubeApiServerTlsVersionnfsubscription.serviceDiscovery.ipConnectFailureThresholdnfsubscription.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenfsubscription.serviceDiscovery.fqdnInMetricsEnablednfsubscription.serviceDiscovery.refreshDelaynfsubscription.serviceDiscovery.timeoutnfsubscription.jetty.commonCpJcMaxPayloadSizeInKBnfsubscription.jetty.maxRequestsHeaderSize
- Modified the default values of the following parameters in the
NF Subscription Microservice (nfsubscription)
section:
nfsubscription.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/liveness-
nfsubscription.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readiness nfsubscription.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Removed the
nfdiscovery.jetty.maxInMemorySizeparameter from the NF Discovery Microservice (nfdiscovery) section because this is handled bynfdiscovery.jetty.commonCpJcMaxPayloadSizeInKBparameter. - Removed the
nfdiscovery.jetty.dnsRefreshDelayparameter from the NF Discovery Microservice (nfdiscovery) section because this is handled bynfdiscovery.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NF Discovery Microservice (nfdiscovery) section:
nfdiscovery.jetty.commonCpJcMaxPayloadSizeInKBnfdiscovery.jetty.maxRequestsHeaderSizenfdiscovery.serviceDiscovery.cipherSuitesnfdiscovery.serviceDiscovery.kubeApiServerTlsVersionnfdiscovery.serviceDiscovery.ipConnectFailureThresholdnfdiscovery.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenfdiscovery.serviceDiscovery.fqdnInMetricsEnablednfdiscovery.serviceDiscovery.refreshDelaynfdiscovery.serviceDiscovery.timeout
- Modified the default values of the following parameters in the
NF Discovery Microservice (nfdiscovery)
section:
nfdiscovery.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/livenessnfdiscovery.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readinessnfdiscovery.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Removed the
nrfauditor.jetty.maxInMemorySizeparameter from the NRFAuditor Microservice (nrfauditor) section because this is handled bynrfauditor.jetty.commonCpJcMaxPayloadSizeInKBparameter. - Removed the
nrfauditor.jetty.dnsRefreshDelayparameter from the NRFAuditor Microservice (nrfauditor) section because this is handled bynrfauditor.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NRFAuditor Microservice (nrfauditor) section:
nrfauditor.serviceDiscovery.cipherSuitesnrfauditor.serviceDiscovery.kubeApiServerTlsVersionnrfauditor.serviceDiscovery.ipConnectFailureThresholdnrfauditor.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenrfauditor.serviceDiscovery.fqdnInMetricsEnablednrfauditor.serviceDiscovery.refreshDelaynrfauditor.serviceDiscovery.timeoutnrfauditor.jetty.commonCpJcMaxPayloadSizeInKBnrfauditor.jetty.maxRequestsHeaderSize
- Modified the default values of the following parameters in the
NRFAuditor Microservice (nrfauditor)
section:
nrfauditor.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/livenessnrfauditor.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readinessnrfauditor.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Added the following parameters in the NF Access Token Microservice(nfaccesstoken) section:
nfaccesstoken.jetty.commonCpJcMaxPayloadSizeInKBnfaccesstoken.jetty.maxRequestsHeaderSizenfaccesstoken.serviceDiscovery.cipherSuitesnfaccesstoken.serviceDiscovery.kubeApiServerTlsVersionnfaccesstoken.serviceDiscovery.ipConnectFailureThresholdnfaccesstoken.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenfaccesstoken.serviceDiscovery.fqdnInMetricsEnablednfaccesstoken.serviceDiscovery.refreshDelaynfaccesstoken.serviceDiscovery.timeout
- Removed the
nfaccesstoken.jetty.dnsRefreshDelayparameter from the NF Access Token Microservice(nfaccesstoken) section because this is handled bynfaccesstoken.serviceDiscovery.refreshDelayparameter. - Modified the default values of the following parameters in the NF Access Token Microservice(nfaccesstoken) section:
nfaccesstoken.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/livenessnfaccesstoken.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readinessnfaccesstoken.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Removed the
nrfartisan.jetty.dnsRefreshDelayparameter from the NRF Artisan Microservice (nrfartisan) section because this is handled by thenrfartisan.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NRF Artisan Microservice (nrfartisan) section:
nrfartisan.serviceDiscovery.cipherSuitesnrfartisan.serviceDiscovery.kubeApiServerTlsVersionnrfartisan.serviceDiscovery.ipConnectFailureThresholdnrfartisan.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenrfartisan.serviceDiscovery.fqdnInMetricsEnablednrfartisan.serviceDiscovery.refreshDelaynrfartisan.serviceDiscovery.timeoutnrfartisan.jetty.commonCpJcMaxPayloadSizeInKBnrfartisan.jetty.maxRequestsHeaderSize
- Modified the default values of the following parameters in the
NRF Artisan Microservice (nrfartisan)
section:
nrfartisan.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/livenessnrfartisan.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readinessnrfartisan.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Removed the
nrfconfiguration.jetty.maxInMemorySizefrom the NRF Configuration Microservice (nrfconfiguration) section because this is handled bynrfconfiguration.jetty.commonCpJcMaxPayloadSizeInKBparameter. - Removed the
nrfconfiguration.jetty.dnsRefreshDelayparameters from the NRF Configuration Microservice (nrfconfiguration) section because this is handled bynrfconfiguration.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NRF Configuration Microservice (nrfconfiguration) section:
nrfconfiguration.serviceDiscovery.cipherSuitesnrfconfiguration.serviceDiscovery.kubeApiServerTlsVersionnrfconfiguration.serviceDiscovery.ipConnectFailureThresholdnrfconfiguration.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenrfconfiguration.serviceDiscovery.fqdnInMetricsEnablednrfconfiguration.serviceDiscovery.refreshDelaynrfconfiguration.serviceDiscovery.timeoutnrfconfiguration.jetty.commonCpJcMaxPayloadSizeInKBnrfconfiguration.jetty.maxRequestsHeaderSize
- Modified the default values of the following parameters in the
NRF Configuration Microservice (nrfconfiguration)
section:
nrfconfiguration.livenessProbe.httpGet.pathfrom /actuator/health/applicationLiveness to /management/health/livenessnrfconfiguration.readinessProbe.httpGet.pathfrom /actuator/health/applicationReadiness to /management/health/readinessnrfconfiguration.startupProbe.httpGet.pathfrom /actuator/health/applicationStartup to /management/health
- Removed the
nrfcachedata.maxInMemorySizeparameter from the NRF Cache Data Microservice (nrfcachedata) section because this is handled bynrfconfiguration.jetty.commonCpJcMaxPayloadSizeInKBparameter. - Removed the
nrfcachedata.jetty.dnsRefreshDelayparameter from the NRF Cache Data Microservice (nrfcachedata) section because this is handled bynrfcachedata.serviceDiscovery.refreshDelayparameter. - Added the following parameters in the NRF Cache Data Microservice (nrfcachedata) section:
nrfcachedata.serviceDiscovery.cipherSuitesnrfcachedata.serviceDiscovery.kubeApiServerTlsVersionnrfcachedata.serviceDiscovery.ipConnectFailureThresholdnrfcachedata.serviceDiscovery.clearCacheOnServiceDiscoveryFailurenrfcachedata.serviceDiscovery.fqdnInMetricsEnablednrfcachedata.serviceDiscovery.refreshDelaynrfcachedata.serviceDiscovery.timeoutnrfcachedata.jetty.commonCpJcMaxPayloadSizeInKBnrfcachedata.jetty.maxRequestsHeaderSize
- Modified the default values of the following parameters in the NRF Cache Data Microservice (nrfcachedata) section:
nrfcachedata.livenessProbe.httpGet.pathfrom/actuator/health/applicationLivenessto/management/health/livenessnrfcachedata.readinessProbe.httpGet.pathfrom/actuator/health/applicationReadinessto/management/health/readinessnrfcachedata.startupProbe.httpGet.pathfrom/actuator/health/applicationStartupto/management/health
- Added the following parameters in the Ingress Gateway Global Parameters section:
enableIntraNfK8sSvcintraNFCommunicationPort
- Modified the default values of the following parameters in the App Info Microservice (appinfo) section:
appinfo.replicationUrifrom"http://mysql-cluster-db-monitor-svc.occne-infra:8080/db-tier/status/replication/realtime"to"http://mysql-cluster-db-monitor-svc.nrf-cndb-ns:8080/db-tier/status/replication/realtime"appinfo.realtimeDbStatusUrifrom"http://mysql-cluster-db-monitor-svc.occne-infra:8080/db-tier/status/cluster/local/realtime"to"http://mysql-cluster-db-monitor-svc.nrf-cndb-ns:8080/db-tier/status/cluster/local/realtime"appinfo.dbTierVersionUrifrom"http://mysql-cluster-db-monitor-svc.occne-infra:8080/db-tier/version"to"http://mysql-cluster-db-monitor-svc.nrf-cndb-ns:8080/db-tier/version"
- Updated the default value of the
perfinfo.overloadManager.ingressGatewayPortparameter from *httpSignalPortRef to *intraNFCommunicationPortRef in the Perf Info Microservice (perf-info) section.
Upgrade, Rollback, and Uninstall Updates
- Updated the upgrade paths in the Supported Upgrade Paths section.
- Updated the rollback paths in the Supported Rollback Paths section.
- Removed the following notes from the Upgrading NRF section
because they are no longer supported.
- While performing a cnDBTier upgrade from 24.1.x versions
and above, cnDBTier uses the
caching_sha2_passwordauthentication plugin for altering the users. Use the following commands for altering the users before cnDBTier upgrade:ALTER USER IF EXISTS 'nrfPrivilegedUsr'@'%' IDENTIFIED WITH 'caching_sha2_password' BY 'nrfPrivilegedPasswd'; ALTER USER IF EXISTS 'nrfApplicationUsr'@'%' IDENTIFIED WITH 'caching_sha2_password' BY 'nrfApplicationPasswd'; - Before upgrading NRF to release 24.3.x, in case NRF
database contains NF Profiles with
dnnattribute anddnnattribute value is not as per 3GPP defined format, NFs should update their NFProfiles with the correctdnnformat (as defined in 3GPP TS 23.003 v16.8 Section 9A). For more information aboutdnnattribute, see Enhancements for dnn NFProfile Attribute and Discovery Query Parameter section in Oracle Communications Cloud Native Core, Network Repository Function User Guide.
- While performing a cnDBTier upgrade from 24.1.x versions
and above, cnDBTier uses the
- Removed the following from the Postupgrade Tasks section:
- content related to Cache Data Microservice which was relevant for install and upgrade for releases that are no longer supported.
- redundant information.
- Removed the following note from the Rolling Back NRF section as
it is no longer applicable.
While performing a cnDBTier rollback to 24.1.x versions, cnDBTier uses the
mysql_native_passwordauthentication plugin for altering the users. Use the following commands for altering the users:ALTER USER IF EXISTS 'nrfPrivilegedUsr'@'%' IDENTIFIED WITH 'mysql_native_password' BY 'nrfPrivilegedPasswd'; ALTER USER IF EXISTS 'nrfApplicationUsr'@'%' IDENTIFIED WITH 'mysql_native_password' BY 'nrfApplicationPasswd'; - Removed the note related to disabling the Subscription Limit feature before rollback from the Rollback Tasks section as it is no longer supported.
- Updated the existing note related to the georedundancy feature in the Rollback Tasks section.
- Restructured the Uninstalling NRF chapter.
Fault Recovery Updates
There are no changes made for this section in this release.