Diameter Handling in Kubernetes(3.0)

This section does not explain how Diameter works in general, but just the special handling needed to run Diameter workflows inside a Kubernetes cluster. 

Since Diameter uses host and domain (Destination-Host and Destination-Realm) for communication, the hostnames need to be setup in the cluster and connected to the pods running the workflows in question. This is done using hostAliases and ClusterIP (which also binds the ports used to the different hostnames/ips).

This chapter describes the following scenarios: 

• Scenario 1: When both Server and Client pods are inside the same Kubernetes cluster.  In the following illustration, the server pod connects using port 3868 and the client pod connects using port 3869. Click here to know more about it.

• Scenario 2: When one pod is outside of the cluster. In the following illustration, the server pod connects using port 3868 and the client connects using port 3869 and, since client is outside the cluster the nodeport 31868 is used. Click here to know more about it.