Failure Scenarios for SIP/RTP services in Container Orchestration Clusters

This paper discusses the issue with scaling SIP/RTP services in a container orchestration cluster such as Kubernetes. In order to run SIP/RTP services in the Kubernetes platform, we require that state and affinity between the two ends, be maintained by the container orchestration cluster. Currently Kubernetes primarily supports stateless services like HTTP. The paper explains the challenge of the Kubernetes overlay network for SIP/RTP services by presenting four failure scenarios with the objective to validate the failure scenarios and present viable solutions. Two of the four failure scenarios have been validated and our approach to counter these failures are presented. One proposed solution is based on a SIP back-to-back user agent or proxy integrated with the Kubernetes environment and a second that leverages the Kubernetes Ingress architecture and services. A third probable solution discussed are the service meshes.