Anthony Bible

@lmangani Thanks for the quick response. Probably not as that would hurt deployments that are using any of those tagged versions (we are). I was hoping we might be able...

+1

> `kubectl describe` on the pod or deployment should help make it clearer which container is crashing and potentially why. There's nothing that looks like a crash in the `destination`...

Oh and for completeness, the liveness and readiness probes: ``` Warning Unhealthy 15m kubelet Readiness probe failed: Get "http://10.2.96.54:9996/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Warning Unhealthy 15m...

I took some time and looked into it. It doesn't look like anything related to Calico or the node. Everything appears to be running on that node with no problems....

So an update, I had this start happening at work with our cluster on GKE so it's not specific to a provider. Also I did try switching to kube-proxy iptables...

Just tried installing it again with 2.12.4 and still getting the same problem: ``` Warning Unhealthy 79s (x2 over 89s) kubelet Liveness probe failed: Get "http://10.2.93.61:9990/live": context deadline exceeded (Client.Timeout...

@olix0r looks like you guys have pprof, would getting a goroutine output help here, maybe something is hanging so it can't mark itself live?

> If there are >10000k results on gitlab.com, this is mabye fixed by #339. Which version are you using and did you try :latest? I just tried `:latest` and that...

@adubovikov thanks, But homer-app currently doesn't use viper to get environment variables only to read the config as far as I can tell . I was referring to this: https://github.com/sipcapture/homer-app/blob/master/docker/docker-entrypoint.d/1