Go to primary content
Oracle® Communications Cloud Native Diameter Routing Agent (CNDRA) Installation Guide
Release 1.0
F16991-02
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

CNDRA Pre-requisites

This section includes information about the required environment for CNDRA deployment.

CNDRA Software

The CNDRA software includes:

The following software must be installed:

Software Version
Kubernetes v1.12.5
HELM v2.11.0

Additional software that needs to be deployed as per the requirement of the services:

Software Chart Version Notes
elasticsearch 1.21.1 Needed for Logging Area
elastic-curator 1.2.1 Needed for Logging Area
elastic-exporter 1.1.2 Needed for Logging Area
logs 2.0.7 Needed for Logging Area
kibana 1.5.2 Needed for Logging Area
grafana 2.2.0 Needed for Metrics Area
metallb 0.8.4 Needed for External IP
metrics-server 2.4.0 Needed for Metric Server
tracer 0.8.3 Needed for Tracing Area

Note:

In case any of the above services are needed and the respective software is not installed in CNE. Please install software before proceeding.
  • Helm must have access to create ClusterRole and ClusterRoleBinding resources.
  • The operator must have their own repository for storing the OCCNDRA images and that repository must be accessible from the kubernetes cluster.

Network access

The Kubernetes cluster hosts must have network access to:

Note:

All the kubectl and helm related commands that are used in this document must be executed on a system depending on the infrastructure of the deployment. It may be some admin server (VM, server, local desktop so on).

Laptop/Desktop Client software

There are some requirements for the client machine where the deployment commands needs to be executed:
  • It should have access to the helm repository and docker image repository.
  • Access to Helm repository must be configured on the client.
  • It should have access to the Kubernetes cluster.
  • It should have necessary environment settings to run the kubectl commands. The environment should have privileges to create namespace in the Kubernetes cluster.
  • It should have helm client installed. The environment should be configured so that the helm install command deploys the software in the Kubernetes cluster.