Hi Pavithra,
Since POD IPs change, you have to rely on DNS records. To have a fixed DNS
name like kamailio.kamalio-service.namespace.svc.cluster.local for a pod
you will have to use StatefullSet, so the pod DNS name doesn't change. Also
you have to use Services and set it to ClusterIP: none, it
Hi Abdirahman,
Do you mean , if I set clusterIP as None, then kubedns server will be
pointing to pod ip so that kubedns/coredns will use pod ip for pod
communication instead of service IP.
Is my understanding correct? From your explanation.
If this is the case, pod ip will be changing whenever
David,
Assuming those are pod ips. Using services doesn’t work since the dns name
> will resolve to a k8s service ip and no the actual pod running the service.
>
If you set *clusterIP: None* in the services, you will get POD IP.
Abdirahman
On Wed, 26 Aug 2020 at 10:48, Pavithra Mohanraja
Hi,
Thanks for the answers.
@David has got my question.
I have a seperate dns server running in my pcscf pod . So in my
/etc/resolv.conf file , I would be configuring
nameserver
in all other cscf pods as well for communication.
My question here is how to change the dns server pointing to
I’ve been trying to figure this out as well.
I haven’t yet found a way of publishing to kube-dns the pod IP of the
running service.
I.e.:
kamailio.whatever.local on ip 10.0.0.1
Rtpengine.whatever.local on ip 10.0.0.2
Appserver.whatever.local on 10.0.0.3
Assuming those are pod ips. Using services
Dear Daniel,
I am just changing my environment. I am using
kamailio+rtpproxy.
while making a call from caller to callee through RTPProxy. Then why only
callee able to listen caller voice .
I use following script snippet.
route[RTPPROXY] {
#!ifdef WITH_NAT
if
Hi Pavithra
You can use the kubedns/CoreDNS of the kubernetes cluster to resolve
Internal DNS records of the pods.To assign DNS records for each POD you
have to deploy a service and set the ClusterIP: none. and the dns record
will be something like
Daniel,
Yes, sorry, there are two issues at discussion here.
1. Use of UUID’s instead of INT. This is kinda moot for us right now. We
switched subscriber to autogenerate UUID, and it’s working great for us. We
don’t really *need* to do this anywhere else currently. I don’t know when I
Daniel,
I have done this, but that’s why I’m confused, because sometimes it works, and
sometimes it doesn’t (with no changes to the configs).
I ran a quick grep on the config:
root@inbound-kamailio-test-02:/usr/local/etc/kamailio# grep -i '#!if'
kamailio.cfg | wc -l
61
