1 Introduction

1.1 Purpose and Scope

The purpose of this document is to highlight the changes made in OCCM in Release 24.1.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 24.1.x To know the list of all the supported versions, see Oracle Communications Cloud Native Core Release Notes.

Release 24.1.0

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

Table 1-1 Compatibility Matrix

Components Compatible Versions
CNE 24.1.x, 23.4.x, 23.3.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 24.1.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 24.1.0:

Table 1-2 Common Services Load Lineup

Common Service Version
Helm Test 24.1.1
Debug Tool 24.1.1

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-3 Preinstalled Software

Software Version
Kubernetes 1.28.6
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-4 Additional Software

Software Version
containerd 1.7.1
Calico 3.26.4
MetalLB 0.13.11
Prometheus 2.50.1
Grafana 9.5.3
Jaeger 1.52.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 24.1.x.

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

Table 1-5 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
  1. occm_custom_values.yaml is updated to include tls configurations. These two flags are introduced occmConfig.cmp.config.tls.enableX509StrictCheck and occmConfig.cmp.config.tls.ignoreCriticalEx
    occmConfig:
  cmp:
    config:
      tls:
        enableX509StrictCheck: true #This field when set false "-x509_strict" will not be included in openssl cmp cmd for strict checking of the X.509 certificates.
        ignoreCriticalExtensionsCheck: false #This field when set true "-ignore_critical" will be included in openssl cmp cmd for checking of X.509 certificate critical extensions.
  2. OCCM network policy occm_network_policy_custom_values_<version>.yaml file is updated to include namespaceSelector in allow-ingress-from-cncc-pods policy.
    # Allow ingress traffic from cncc pods
- metadata:
    name: allow-ingress-from-cncc-pods
  spec:
    podSelector:
      matchLabels:
        app.kubernetes.io/part-of: occm
    policyTypes:
    - Ingress
    ingress:
    - from:
      - namespaceSelector:
          matchLabels: { }
          ## kubernetes.io/metadata.name: cncc-ns
      - podSelector:
          matchLabels:
            app.kubernetes.io/app-name: cncc
Changes in the resource information for custom_values.yaml file No No changes are made.
Changes in the CSAR package No No changes are made.

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 are made.

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 are made.

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-6 Resource Profile

Microservice Name Pod Replica Limits Requests
CPU Memory (Gi) Ephimeral Storage (Mi) CPU Memory (Gi) Ephimeral Storage (Mi)
OCCM 1 2 2 1102 2 12 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 implemented on demand when Helm test command is run. It will run the Helm test and stops after completion. These are short-lived jobs that get terminated after the work is done. So, they are not part of active deployment resource but need to be considered only during Helm test procedures.
  • Troubleshooting Tool (Debug tool) Container - If Troubleshooting Tool Container Injection is enabled during OCCM deployment or upgrade, this container will be injected to OCCM pod. These containers will stay till pod or 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.