Diameter Server and Client Inside Same Kubernetes Cluster(4.3)

Assume that GCP Kubernetes Cluster is created beforehand based on various cloud providers installation guide here.

This section describes how to setup Diameter Server and Diameter Client hosted in the same Kubernetes Cluster. For example, Diameter Server and Diameter Client hosted in GCP Kubernetes Cluster.

Assumed that Diameter Server and Diameter Client workflows have been created with the following configurations.

	Diameter Server	Diameter Client

	Diameter Server	Diameter Client
Hostname	server-digitalroute-com	client-digitalroute-com
Dynamic Workflow enabled	Yes	Yes
Bind On All Interfaces	Yes	Yes
Diameter Debug Event enabled	Yes	Yes
Diameter Port	3868	3869
Network Protocol	TCP	TCP
Diameter Realm	digitalroute.com	digitalroute.com

For this to work (using Diameter in an ECD in Kubernetes), in the Diameter Stack agent the checkbox “Bind On All Interfaces” under the “Advanced”-tab needs to be checked. This is true regardless of if the localhost ip is used or the ip connected with the LoadBalancer service.

To run these Diameter Server and Diameter Client workflows, deploy an ECD pod for each workflow respectively. Therefore, login to desktop-online Web UI, go to Manage menu, select EC Deployment > New EC Deployment.

New EC Deployment

To deploy an ECD Pod for Diameter Server workflow on the cluster, follow these steps:

On the Configure EC Tab, fill in the EC Deployment Name and the rest of the fields if needed. Click Next to continue.
On the Configure Auto Scale Tab, do not enable Auto Scaling. Click Next to continue.
On the Configure Workflow Tab, create a new real time workflow from the selected workflow template i.e., Diameter Server or Diameter Client (either one). Click Next to continue.
On the Configure Network Tab, create a Network Service type ClusterIP with appropriate port. The Service Name must be set to the Diameter Server or Diameter Client hostname.

	Diameter Server	Diameter Client

	Diameter Server	Diameter Client
Service Name	server-digitalroute-com	client-digitalroute-com
ClusterIP Port	3868	3869

Before finalise the EC deployment, check and verify EC Deployment by pressing “View YAML“.

For instance, the Diameter Server YAML content looks like this:

apiVersion: "mz.digitalroute.com/v1alpha1"
kind: "ECDeployment"
metadata:
  creationTimestamp: "2024-09-09T03:41:05.000000Z"
  name: "ecd-server-digitalroute-com"
  namespace: "uepe"
  resourceVersion: "6342188"
  uid: "260e7271-14b7-43e7-8fb5-4535bb630f1d"
spec:
  jvmArgs:
  - "Xmx512M"
  - "Xms512M"
  manualUpgrade: false
  persistence:
    pvcName: "ec1-filestore-pvc"
  ports:
  - containerPort: 3868
    protocol: "TCP"
  resources:
    limits:
      memory: "640Mi"
    requests:
      memory: "640Mi"
  services:
  - name: "server-digitalroute-com"
    spec:
      ports:
      - name: "port-1"
        port: 3868
        protocol: "TCP"
        targetPort: 3868
      type: "ClusterIP"
  workflows:
  - instances:
    - name: "Diameter_Server"
      parameters: "{}"
      useExtRef: "{}"
    template: "Diameter.DiameterDCCAServerSimulator"

For instance, the Diameter Client YAML content looks like this:

apiVersion: "mz.digitalroute.com/v1alpha1"
kind: "ECDeployment"
metadata:
  creationTimestamp: "2024-09-09T03:42:56.000000Z"
  name: "ecd-client-digitalroute-com"
  namespace: "uepe"
  resourceVersion: "6343337"
  uid: "b4e223b7-75ff-453f-bdea-c8f73b5e0342"
spec:
  jvmArgs:
  - "Xmx512M"
  - "Xms512M"
  manualUpgrade: false
  persistence:
    pvcName: "ec1-filestore-pvc"
  ports:
  - containerPort: 3869
    protocol: "TCP"
  resources:
    limits:
      memory: "640Mi"
    requests:
      memory: "640Mi"
  services:
  - name: "client-digitalroute-com"
    spec:
      ports:
      - name: "port-1"
        port: 3869
        protocol: "TCP"
        targetPort: 3869
      type: "ClusterIP"
  workflows:
  - instances:
    - name: "Diameter_Client"
      parameters: "{}"
      useExtRef: "{}"
    template: "Diameter.DiameterClientSimulator"

Now, finalise EC Deployment by clicking Finish. Choose not to enable the ECD for now.

Repeat step 1 till step 4 to deploy another ECD Pod for Diameter Client workflow on the same cluster.

Following the creation of both ECD, let’s monitor the Kubernetes Services type ClusterIP that is being created.

Execute this command:

kubectl get svc -n uepe

On the cluster, the is the output.

Kubernetes creates DNS records for Services and Pods. You can contact Services with consistent DNS names instead of IP addresses.

The Service Name in the form of <service-name>.<namespace> resolves to the cluster IP of the Service. <namespace> can be omitted if both ECD are located in the same namepsace, i.e., uepe

Next, user may select and enable both ECD on the cluster one by one via the desktop-online WEB UI respectively.

Select and Enable ECD

To view Diameter Server workflow debug log, go back to the Manage menu. Select Execution Manager > Running Workflows.

Select the Diameter Server workflow that is currently running and click Open Monitor.

Then select Enable Debug and select Diameter Stack agent in the agent debug panel to view the debug log.

If connection established successfully between Diameter Server and Diameter Client, Capabilities-Exchange pair messages and repeat Device Watchdog messages are seen in the agent debug panel.

(The following section is Deprecated)

The following examples shows how to setup both Diameter server and client inside the same cluster.

First setup the Server and Client clusterIPs in their respective yaml files as shown in the following examples. The selector part binds the IP address to the correct ECD. The ECD should only contain one pod. The port is cluster-global, which means that two ECDs can’t use the same port (as listening port).

The listening port for the two server workflows are 3868 (server), 3870 (backupserver), and 3869 (client).

The string ecd: client matches the same string under labels in the ECD yaml shown further below. See example.
1. Run the following command to get the IP address for the ECD:
  For example:
2. Run the following command:
Since the server needs to have information about both the client and server hostnames, so both the hostnames need to be configured for both ECDs.
The following examples (for the client and server) is just an excerpt of the full ECD to show how to use hostnames:

The following is an example of a full ECD - one Diameter client and two Diameter servers (three peers). The hostnames must be included in the yaml file irrespective of the fact if it is for client or server.

Example - Full server-ecd
1. Run the following command:

Usage Engine Private Edition 4 Documentation

Diameter Server and Client Inside Same Kubernetes Cluster(4.3)

Example - Full client ecd