ingress-nginx: Controller first boot (or two) fails when combined with istio-proxy

Hey, I’ve observed this behaviour, which is the container failing to boot one or two times with every update we do.

❯ kn logs -p nginx-ingress-controller-58688765db-hxlzq nginx-ingress-controller
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:    0.10.0
  Build:      git-0836cb30
  Repository: https://github.com/aledbf/ingress
-------------------------------------------------------------------------------

I0124 08:33:25.301191       6 main.go:181] Creating API client for https://10.178.0.1:443
F0124 08:33:25.303541       6 main.go:236] Error while initializing connection to Kubernetes apiserver. This most likely means that the cluster is misconfigured (e.g., it has invalid apiserver certificates or service accounts configuration). Reason: Get https://10.178.0.1:443/version: dial tcp 10.178.0.1:443: getsockopt: connection refused
Refer to the troubleshooting guide for more information: https://github.com/kubernetes/ingress-nginx/blob/master/docs/troubleshooting.md

Then it’ll crash, and come back to life:

❯ kn logs nginx-ingress-controller-58688765db-hxlzq nginx-ingress-controller
-------------------------------------------------------------------------------
NGINX Ingress controller
  Release:    0.10.0
  Build:      git-0836cb30
  Repository: https://github.com/aledbf/ingress
-------------------------------------------------------------------------------

I0124 08:33:27.712235       7 main.go:181] Creating API client for https://10.178.0.1:443
I0124 08:33:27.723704       7 main.go:193] Running in Kubernetes Cluster version v1.8+ (v1.8.6-gke.0) - git (clean) commit ee9a97661f14ee0b1ca31d6edd30480c89347c79 - platform linux/amd64

Any ideas?