Jambonz -- SIP POD is always in CrashLoopBackOff state about helm-charts HOT 6 OPEN

I think the issue is that the drachtio image in the sip daemonset needs to dynamically determine the ip address it should listen on. Most often, there is a private IP that the drachtio server binds to, as well as a public address assigned over the top. On cloud providers, like AWS, there is typically a metadata http request that can be made to determine the IPs.

Since you are running on bare metal, we can not use this requests to automagically determine the IPs. Instead, could you define these environment variables for the drachtio container in the sbc-sip daemonset:

LOCAL_IP
PUBLIC_IP

from helm-charts.

If you look at the entrypoint.sh file in the drachtio container, I think you will see what I am getting at..

from helm-charts.

So ideally, I will be using the DownwardAPI for the local IP and for the PUBLIC_IP, I'll have to assign it manually.. Please correct me if I'm wrong here.

I apologize for these botherations, but this is our project to deploy and we dont have any documentation except asking here.

from helm-charts.

I think I can use both LOCAL_IP and PUBLIC_IP from the DownwardAPI of Kubernetes

here is the link -- if you can suggest a better approach

https://kubernetes.io/docs/concepts/workloads/pods/downward-api/

spec.nodeName
the name of the [node](https://kubernetes.io/docs/concepts/architecture/nodes/) where the Pod is executing
status.hostIP
the primary IP address of the node to which the Pod is assigned
status.podIP
the pod's primary IP address (usually, its IPv4 address)

from helm-charts.

you should join my slack channel -- just go to https://joinslack.jambonz.org

from helm-charts.

joining in

from helm-charts.