3 Offline Mediation Controller Cloud Native System Requirements
Learn about the software that is compatible with the Oracle Communications Offline Mediation Controller cloud native deployment package. This package uses Docker, Kubernetes, Helm, and Linux for containerization and orchestration.
Topics in this document:
Offline Mediation Controller Cloud Native Deployment Software Compatibility
Caution:
It is the responsibility of the system administrator to ensure that all installed software dependencies are kept up to date wherever possible. Oracle supports versions of the software where the software vendor declares backward compatibility to the version certified with Offline Mediation Controller and where the upgrade is a minor version increment (that is, A.B.C to A.B.D).
It is particularly important for system administrators to adopt this policy for software dependencies for which upgrades are generally related to security rather than focused on functionality.
The Offline Mediation Controller cloud native images were validated with the software listed in Table 3-1.
Table 3-1 Supported Software for Offline Mediation Controller Cloud Native Deployment Package
| Software | Version | Notes |
|---|---|---|
|
Kubernetes |
1.29.x |
N/A |
|
Helm |
3.14.0 |
N/A |
| Helidon | 1.4.13 | N/A |
|
Fluentd |
1.16.3 |
N/A |
|
Grafana |
10.0.1 |
N/A |
|
Prometheus |
2.48.1 |
N/A |
|
Prometheus Alertmanager |
0.26.0 |
N/A |
|
Prometheus Operator |
0.70.0 |
N/A |
| Prometheus JMX Exporter Java Agent | 0.19.0 | N/A |
Third-Party Platforms
Offline Mediation Controller cloud native is designed to be agnostic of the underlying cloud infrastructure. It relies on standard APIs, objects and configuration functions from the software products listed in this document. As such, Offline Mediation Controller cloud native is certified on any container platform based on a CNCF-certified Kubernetes, provided the version requirements listed in this document are satisfied.