Managing Diameter Event Logger
The following example YAML Kubernetes deployment file demonstrates how to deploy Diameter Event Logger.
This file uses the following terms:
<YOUR_NAMESPANCE_NAME>
— The Kubernetes namespace. For example,matrixx
.<YOUR_DOCKER_REGISTRY>
— The Docker registry. Usually the same Docker registry as the MATRIXX images.<VERSION>
— The Diameter Event Logger version number.<YOUR_DEBUG_LEVEL>
— The debug level. For example,INFO
.<YOUR_NFS_IP>
— The IP address of the Network File System (NFS) server.<YOUR_FOLDER_NAME>
— The path to the NFS directory.
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: <YOUR_NAMESPANCE_NAME>
name: diameter-event-logger
spec:
replicas: 1
selector:
matchLabels:
app: diameter-event-logger
template:
metadata:
labels:
app: diameter-event-logger
spec:
containers:
- name: diameter-event-logger
image: <YOUR_DOCKER_REGISTRY>/diameter-event-logger:<VERSION>
imagePullPolicy: Always
env:
- name: "DIAMETER_EVENT_LOGGER_LOG_LEVEL"
value: "<YOUR_DEBUG_LEVEL>"
volumeMounts:
- mountPath: /opt/mtx/data
name: vol-data
- mountPath: /opt/mtx/conf
name: sideloader-sync-dir
initContainers:
- name: diameter-event-logger-sideloader
image: <YOUR_DOCKER_REGISTRY>/diameter-event-logger-sideloader:<VERSION>
imagePullPolicy: Always
env:
- name: MTX_SYNC_TARGET_DIRS
value: /opt/mtx/conf
volumeMounts:
- mountPath: /sync
name: sideloader-sync-dir
- name: busybox
image: busybox
imagePullPolicy: IfNotPresent
command: ['sh', '-c', "chown -R 1000:1000 /opt/mtx/"]
volumeMounts:
- mountPath: /opt/mtx/data
name: vol-data
- mountPath: /opt/mtx/conf
name: sideloader-sync-dir
volumes:
- name: vol-data
persistentVolumeClaim:
nfs:
server: <YOUR_NFS_IP>
path: <YOUR_FOLDER_NAME>
- name: sideloader-sync-dir
emptyDir: {}