I usually recommend considering if you really need to do it, the (added) large complexity is in most cases not worth the (small) benefit.


If you want to go for it anyway, one way of doing it is just binding the public IP(s) to individual Kamailio instances. Using an IP load balancer to have multiple Kamailio server behind a single IP only works in limited scenarios (stateless). In the end it boils down the usual deployment and configuration challenges one has to deal on k8s.







Henning Westerholt – https://skalatan.de/blog/

Kamailio services – https://gilawa.com


From: Calvin E. <calvine@gmail.com>
Sent: Dienstag, 28. März 2023 23:20
To: sr-users@lists.kamailio.org
Subject: [SR-Users] Rancher, AWS, and Elastic IP


I'm looking for documentation//howto/advice/best practices for running Kamailio under Kubernetes on AWS via Rancher. Specifically, how to manage the public/Elastic IP. This is a load balancer (dispatcher) scenario with rtpengine for receiving inbound calls from a DID provider, but a similar configuration might be used for clients. I'm open to using an AWS load balancer, and would like to scale with multiple Kamailio pods behind a single public IP. I'd rather use Rancher-managed EC2 than pay extra for EKS, unless EKS can cancel out its own cost. This sounds like it should be a solved problem, just complex. I see blogs and videos out there, but it's not always obvious if their content is current. Anyone want to help me peel this onion?