Introduction

1.1 Purpose and Scope

The purpose of this document is to highlight the changes made in OCCM in Release 23.4.x. These changes may have an impact on the customer network operations and should be considered by the customer while planning the deployment.

1.2 OCCM 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.4

There is no change in the compatibility matrix in this release.

Release 23.4.3

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

Table 1-1 Compatibility Matrix

Components	Compatible Versions
CNE	23.4.x, 23.3.x, 23.2.x
CDCS	23.4.x, 23.3.x

Release 23.4.2

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

Table 1-2 Compatibility Matrix

Components	Compatible Versions
CNE	23.4.x, 23.3.x, 23.2.x
CDCS	23.4.x, 23.3.x

Release 23.4.1

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

Table 1-3 Compatibility Matrix

Components	Compatible Versions
CNE	23.4.x, 23.3.x, 23.2.x
CDCS	23.4.x, 23.3.x

Release 23.4.0

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

Table 1-4 Compatibility Matrix

Components	Compatible Versions
CNE	23.4.x, 23.3.x, 23.2.x
CDCS	23.4.x, 23.3.x

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.

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

Table 1-5 Common Services Load Lineup

Common Service	Version
Helm Test	23.4.3
Debug Tool	23.4.3

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

Table 1-6 Common Services Load Lineup

Common Service	Version
Helm Test	23.4.2
Debug Tool	23.4.2

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

Table 1-7 Common Services Load Lineup

Common Service	Version
Helm Test	23.4.1
Debug Tool	23.4.1

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

Table 1-8 Common Services Load Lineup

Common Service	Version
Helm Test	23.4.0
Debug Tool	23.4.1

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

Table 1-9 Common Services Load Lineup

Common Service	Version
Helm Test	23.4.0
Debug Tool	23.4.0

1.4 Software Requirements

This section lists the software that must be installed before installing OCCM:

Install the following software before installing OCCM:

Table 1-10 Preinstalled Software

Software	Version
Kubernetes	1.27.x, 1.26.x, 1.25.x
Helm	3.12.3
Podman	4.4.1

To check the current Helm and Kubernetes version installed in the CNE, run the following commands:

 kubectl version

 helm version

The following software are available if OCCM is deployed in CNE. If you are deploying OCCM in any other cloud native environment, these additional software must be installed before installing OCCM. To check the installed software, run the following command:

helm ls -A

The list of additional software items, along with the supported versions and usage, is provided in the following table:

Table 1-11 Additional Software

Software	Version
containerd	1.7.5
Calico	3.25.2
MetalLB	0.13.11
Prometheus	2.44.0
Grafana	9.5.3
Jaeger	1.45.0
Istio	1.18.2
Kyverno	1.9.0
cert-manager	1.12.4
Oracle OpenSearch	2.3.0
Oracle OpenSearch Dashboard	2.3.0
Fluentd OpenSearch	1.16.2
Velero	1.12.0

1.5 Orchestration

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

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

Table 1-12 Orchestration

Orchestration Changes	Status	Notes
Support for in-service upgrade	Yes	Upgrade and Rollback is supported. Note that OCCM microservices are single pod.
Changes in the custom_values.yaml file	Yes	For information about changes in the custom_values.yaml file, see Helm section
Changes in the resource information for custom_values.yaml file	No	No changes have been made in this release.
Changes in the CSAR package	No	No changes have been made in this release. CSAR package is supported. Note: For more information on specific CSAR changes, please contact My Oracle Support.
Changes in Role-Based Access Control (RBAC) policy	No	No changes have been made in this release. OCCM deployment needs Service Account. Appropriate permissions must be assigned to OCCM using Kubernetes Service Account, Role and Role Binding, based on the selected deployment model.
Changes in Life Cycle Management (LCM) Operations	No	No changes have been made in this release. OCCM deployment using helm install and CDCS is supported.
Helm Test Support	Yes	Helm test is supported.

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

Table 1-13 Orchestration

Orchestration Changes	Status	Notes
Support for in-service upgrade	Yes	Upgrade and Rollback is supported. Note that OCCM microservices are single pod.
Changes in the custom_values.yaml file	No	No changes have been made in this release.
Changes in the resource information for custom_values.yaml file	No	No changes have been made in this release.
Changes in the CSAR package	No	No changes have been made in this release. CSAR package is supported. Note: For more information on specific CSAR changes, please contact My Oracle Support.
Changes in Role-Based Access Control (RBAC) policy	No	No changes have been made in this release. OCCM deployment needs Service Account. Appropriate permissions must be assigned to OCCM using Kubernetes Service Account, Role and Role Binding, based on the selected deployment model.
Changes in Life Cycle Management (LCM) Operations	No	No changes have been made in this release. OCCM deployment using helm install and CDCS is supported.
Helm Test Support	Yes	Helm test is supported.

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

Table 1-14 Orchestration

Orchestration Changes	Status	Notes
Support for in-service upgrade	Yes	Upgrade and Rollback is supported. Note that OCCM microservices are single pod.
Changes in the custom_values.yaml file	No	No changes have been made in this release.
Changes in the resource information for custom_values.yaml file	No	No changes have been made in this release.
Changes in the CSAR package	No	No changes have been made in this release. CSAR package is supported. Note: For more information on specific CSAR changes, please contact My Oracle Support.
Changes in Role-Based Access Control (RBAC) policy	No	No changes have been made in this release. OCCM deployment needs Service Account. Appropriate permissions must be assigned to OCCM using Kubernetes Service Account, Role and Role Binding, based on the selected deployment model.
Changes in Life Cycle Management (LCM) Operations	No	No changes have been made in this release. OCCM deployment using helm install and CDCS is supported.
Helm Test Support	Yes	Helm test is supported.

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

Table 1-15 Orchestration

Orchestration Changes	Status	Notes
Support for in-service upgrade	Yes	Upgrade and Rollback is supported. Note that OCCM microservices are single pod.
Changes in the custom_values.yaml file	No	No changes have been made in this release.
Changes in the resource information for custom_values.yaml file	No	No changes have been made in this release.
Changes in the CSAR package	No	No changes have been made in this release. CSAR package is supported. Note: For more information on specific CSAR changes, please contact My Oracle Support.
Changes in Role-Based Access Control (RBAC) policy	No	No changes have been made in this release. OCCM deployment needs Service Account. Appropriate permissions must be assigned to OCCM using Kubernetes Service Account, Role and Role Binding, based on the selected deployment model.
Changes in Life Cycle Management (LCM) Operations	No	No changes have been made in this release. OCCM deployment using helm install and CDCS is supported.
Helm Test Support	Yes	Helm test is supported.

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

Table 1-16 Orchestration

Orchestration Changes	Status	Notes
Support for in-service upgrade	Yes	Upgrade and Rollback is supported. Note that OCCM microservices are single pod.
Changes in the custom_values.yaml file	Yes	OCCM and OCCM Network Polices Helm chart and custom values are made available as part of OCCM package.
Changes in the resource information for custom_values.yaml file	Yes	OCCM resource requirement is updated in custom values file.
Changes in the CSAR package	Yes	CSAR package is supported. Note: For more information on specific CSAR changes, please contact My Oracle Support.
Changes in Role-Based Access Control (RBAC) policy	Yes	OCCM deployment needs Service Account. Appropriate permissions must be assigned to OCCM using Kubernetes Service Account, Role and Role Binding, based on the selected deployment model.
Changes in Life Cycle Management (LCM) Operations	Yes	OCCM deployment using helm install and CDCS is supported.
Helm Test Support	Yes	Helm test is supported.

1.6 Resource Requirements

This section lists the resource requirements to install and run OCCM

Resource Profile

Table 1-17 Resource Profile

Microservice Name	Pod Replica	Limits			Requests
Microservice Name	Pod Replica	CPU	Memory (Gi)	Ephimeral Storage (Mi)	CPU	Memory (Gi)	Ephimeral Storage (Mi)
OCCM	1	2	2	1102	2	2	57
Helm Test	1	0.5	0.5	1102	0.5	0.5	57
Total		2.5	2.5	2204	2.5	2.5	114

Note:

Helm Test Job - This job is executed on demand when helm test command is executed. It will execute the helm test and stops after completion. These are short-lived jobs which gets terminated after the work is done. So, they are not part of Active deployment Resource but needs to be considered only during helm test procedures.
Troubleshooting Tool (Debug tool) Container - If Troubleshooting Tool Container Injection is enabled during OCCM deployment/upgrade, this container will be injected to OCCM pod. These containers will stay till pod/deployment exists. Debug tool resources are not considered in the calculation. Debug tool resources usage is per pod, if debug tool is enabled then max 0.5vCPU and 0.5Gi Memory per occm pod is needed.

1 Introduction