Diameter Notifier Configuration

Diameter Notifier configuration includes general properties and TLS properties.

Diameter Notifier Properties describes the properties for configuring Diameter Notifier.

Table 1. Diameter Notifier Properties
Property	Type	Default	Description
notifier.image.name	String	matrixx-diameter/diameter-notifier-reference	The Diameter Notifier container image.
notifier.image.version	Integer	1.0.0	The tag for Diameter Notifier container image.
notifier.configuration	String		List of environment variables to inject into Diameter Notifier configuration.
notifier.replicaCount	Integer	1	The number of Diameter Notifier scale instances.
notifier.logging.level.info	String	info	The Diameter Notifier logging level.
notifier.service.http.port	Integer	8080	HTTP server port for the Diameter Notifier (health service, Prometheus, and so forth). In most environments, this should not be changed..
notifier.service.grpc.port	Integer	50051	The gRPC port of the Diameter Notifier. Diameter Gateway sends a gRPC request to the Diameter Notifier through this port.
notifier.service.grpc.engine	Integer	14061	Engine callback port. The engine sends requests through this port.
notifier.ports	Integer	8080, 14061	List of ports to expose from the container.
notifier.resources.limits.cpu	Integer	1	Specifies the container CPU limit in Kubernetes Units.
gateway.resources.requests.cpu	Integer	250m	Specifies the request CPU limit in Kubernetes Units.

Diameter Notifier TLS Configuration

Diameter Notifier TLS Configuration Properties describes the Diameter Notifier TLS configuration properties.

Table 2. Diameter Notifier TLS Configuration Properties
Property	Type	Default	Description
notifier.configuration.MDD_CLIENT_TLS_ENABLE	Boolean	False	If `true`, the MDD client connection towards Diameter Gateway is established with TLS.
notifier.configuration.MDD_CLIENT_TLS_INSECURESKIPVERIFY	Boolean	False	If `false`, the TLS connection is validated with the certificate file from the notifier.configuration.MDD_CLIENT_TLS_CAFILE parameter.
notifier.configuration.MDD_CLIENT_TLS_CAFILE	String	opt/mtx/conf/keystore/notifier/ca.crt	If the following property is `false`, this is the path to the certificate file: notifier.configuration.MDD_CLIENT_TLS_INSECURESKIPVERIFY
notifier.configuration.MDD_SERVER_TLS_ENABLE	Boolean	False	If `true`, the MDD server connection from MATRIXX Engine is established with TLS.
notifier.configuration.MDD_SERVER_TLS_SELFSIGNEDCERT	Boolean	False	If `false`, the TLS connection is established with the key and certificate files from the notifier.configuration.MDD_SERVER_TLS_CERTFILE and notifier.configuration.MDD_SERVER_TLS_KEYFILE parameter.
notifier.configuration.MDD_SERVER_TLS_CERTFILE	String	/opt/mtx/conf/keystore/notifier/tls.crt	If the following property is `false`, this is the path to the certificate file: notifier.configuration.MDD_SERVER_TLS_SELFSIGNEDCERT
notifier.configuration.MDD_SERVER_TLS_KEYFILE	String	/opt/mtx/conf/keystore/notifier/tls.key	If the following property is `false`, this is the path to the key file: notifier.configuration.MDD_SERVER_TLS_SELFSIGNEDCERT
global.tls.secretName.notifier	String	diameter-gateway-notifier-tls	The Kubernetes Secret name for Diameter Notifier.

You must create a Kubernetes Secret to load certificate and key files into the pod. Diameter Notifier looks up the secret name and, by default, mounts on /opt/mtx/conf/keystore/notifier. For example:

apiVersion: v1
kind: Secret
metadata:
  name: diameter-gateway-notifier-tls
type: kubernetes.io/tls
data:
  ca.crt: {{ .Files.Get "certs/notifier/ca.crt" | b64enc }}
  tls.crt: {{ .Files.Get "certs/notifier/tls.crt" | b64enc }}
  tls.key: {{ .Files.Get "certs/notifier/tls.key" | b64enc }}

Diameter Notifier Helm Values File

The following example shows a Diameter Notifier Helm values file configuration:

notifier:
  enable: false
 
  image:
    name: "diameter-notifier"
    version: "v3.0.2"
 
  configuration:
    HTTP_PORT: 8080
    MDD_PORT: 14061
    WATCHER_DEPLOYMENTNAME: diameter-gateway
    WATCHER_PORTNAME: grpc
    WATCHER_CALLBACKPORTNAME: engine
    WATCHER_NAMESPACE: default
    EXTENSION_SCHEMA: false
    MDD_CLIENT_TLS_ENABLE: false
    MDD_CLIENT_TLS_INSECURESKIPVERIFY: false
    MDD_CLIENT_TLS_CAFILE: "/opt/mtx/conf/keystore/notifier/ca.crt"
    MDD_SERVER_TLS_ENABLE: false
    MDD_SERVER_TLS_SELFSIGNEDCERT: false
    MDD_SERVER_TLS_CERTFILE: "/opt/mtx/conf/keystore/notifier/tls.crt"
    MDD_SERVER_TLS_KEYFILE: "/opt/mtx/conf/keystore/notifier/tls.key"
   
  replicaCount: 1
     
  logging:
    level: info
   
  service:
    type: ClusterIP
    http:
      port: 8080
      targetPort: 8080
    grpc:
      port: 50051
      targetPort: 50051
    engine:
      port: 14061
      targetPort: 14061
 
  ports:
    - containerPort: 8080
      name: http
    - containerPort: 14061
      name: engine
 
  resources:
    limits:
      cpu: 1
    requests:
      cpu: 250m