2 cnDBTier Features

This chapter lists the added or updated features in release 25.1.2xx. For more information about the features, see Oracle Communications Cloud Native Core, cnDBTier User Guide.

Release 25.1.201-4

There are no new features or feature enhancements in this release.

Release 25.1.201-3

There are no new features or feature enhancements in this release.

Release 25.1.201-2

Oracle Communications Cloud Native Core, cnDBTier includes the following enhancement:

Migration from SpringBoot to Micronaut:

cnDBTier supports Micronaut from 25.1.201-2 onwards. The URL for Prometheus scrape has changed from /actuator/prometheus to /prometheus.

Release 25.1.201-1

There are no new features or feature enhancements in this release.

Release 25.1.201

There are no new features or feature enhancements in this release.

Release 25.1.200

Oracle Communications Cloud Native Core, cnDBTier includes the following features or enhancements:
  • Support for cnDBTier Backup Status APIs in CNC Console:

    With this enhancement, cnDBTier NDB Backup status can be viewed on CNCC Console GUI. NF applications can check if the NDB cluster is performing a backup. This helps to prevent NF schema changes that may cause upgrade failures using the new screen. Additionally, a new API is added for this enhancement.

    For more information on the Backup Status API, see the "cnDBTier APIs" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.

  • cnDBTier Metrics reorganization:

    In the earlier implementation, metrics collection followed a centralized model where all metrics were gathered solely through the monitoring service. While functional, this approach led to performance bottlenecks. The monitoring service became heavily loaded, resulting in slow metrics retrieval and, at times, resource spillage in terms of CPU and memory consumption. To address these issues, the metrics collection process has been distributed. Wherever feasible, metrics are now offloaded to the respective microservices. This decentralization reduces the load on the central monitor service, significantly improving the efficiency and speed of metrics retrieval.

    As part of this new design, the infrastructure monitor component has been embedded as a permanent container within each relevant microservice. While this increases the overall resource footprint, it ensures a more scalable, responsive, and resilient monitoring framework.

    Note:

    With multiple distributed endpoints now serving metrics, Prometheus must be appropriately scaled/resourced to handle the increased load and maintain scraping efficiency.
    For more information on cnDBTier Metrics, see the "Metrics" section in Oracle Communications Cloud Native Core, cnDBTier User Guide.
  • Support for ASM 1.21.6:

    cnDBTier 25.1.200 supports Aspen Service Mesh (ASM) 1.21.6 version on Kubernetes 1.27 version from this release.

  • Support for HTTPS communication:

    The initial HTTPS implementation in DBTier had several limitations. There was full support to support scenarios such as transitioning from HTTPS disabled to enabled (and vice versa), nor did it account for HTTPS support on cnLB. These gaps resulted in incomplete HTTPS functionality across different deployment states.

    With the current implementation, these issues have been comprehensively addressed. The enhanced solution ensures full-fledged HTTPS support throughout DBTier, including:

    • Seamless transition between HTTPS enabled and disabled states
    • Robust handling of HTTPS across all relevant components, including cnLB
    • Consistent and reliable secure communication in all configurations

    This update guarantees end-to-end HTTPS functionality, improving security and system consistency in various deployment scenarios.

    For more information about this feature enhancement, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
  • Support for Dual Stack:

    cnDBTier supports deployment on dual stack Kubernetes infrastructure, enabling communication over both IPv4 and IPv6. Using the dual stack mechanism, cnDBTier can establish and accept connections within pods and services using either IP family and interact seamlessly with external systems that support IPv4 and IPv6.

    In this setup, cnDBTier can use IPv4 or IPv6 for internal communication between its microservices, while external communication can be independently configured to use IP family. Additionally, the preferred IP family can be changed dynamically after deployment, providing enhanced flexibility in managing network configurations.

    For more information about this feature enhancement, see Oracle Communications Cloud Native Core, cnDBTier User Guide and Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.
  • cnDBTier Helm (MOP) Enhancements:

    Starting with version 25.1.200, cnDBTier supports the automated creation of service accounts, roles, and role bindings. While this functionality was available in older versions, the latest release introduces validation for manually created service accounts. Helm charts now verify whether a manually created service account has the required permissions.

    The configuration has also been restructured to support different service accounts, including:
    • Upgrade service account
    • Application service account
    • Multus service account
    For detailed configuration instructions, refer to the Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide.