Liveness and Readiness are all refused

[tianweipeng]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

NGINX Ingress controller version:nginx-ingress-0.25.0

Kubernetes version (use kubectl version):1.15.0

Environment:

• Cloud provider or hardware configuration: hp + virtualbox
• OS (e.g. from /etc/os-release): centos7.6
• Kernel (e.g. uname -a): 3.10.0-957.el7.x86_64
• Install tools:kubeadm
• Others:network plug-in is calico lasted and with ipvs
  --

What happened:
my ingress-controllers randomly go into CrashLoopBackOff because the liveness and readiless are both connection refused

What you expected to happen:
describe pod see this

Warning Unhealthy 5s (x5 over 45s) kubelet, k8s.node01.com Readiness probe failed: Get http://192.168.88.137:10254/healthz: dial tcp 192.168.88.137:10254: connect: connection refused
Warning Unhealthy 4s (x4 over 44s) kubelet, k8s.node01.com Liveness probe failed: Get http://192.168.88.137:10254/healthz: dial tcp 192.168.88.137:10254: connect: connection refused

it can't connect to the pod and go to CrashLoopBackOff

kubectl logs see this
[root@k8s ~]# kubectl logs nginx-ingress-controller-7995bd9c47-rtrzq -n ingress-nginx

NGINX Ingress controller
Release: 0.25.0
Build: git-1387f7b7e
Repository: https://github.com/kubernetes/ingress-nginx

W0823 11:30:38.996730 6 flags.go:221] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)
nginx version: openresty/1.15.8.1
W0823 11:30:39.003694 6 client_config.go:541] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I0823 11:30:39.004058 6 main.go:183] Creating API client for https://10.96.0.1:443

How to reproduce it (as minimally and precisely as possible):
sorry i'm not familiar with inginx-ingress.i deploy it with official doc 0.25.0 https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml
but it happened to me.

Anything else we need to know:
but when i add template: spec: hostNetwork: true. everything is ok .i want know how can use it without hostNetwork: true. very thanks!!!

[D1987]

I've got the same strange behavior in GKE.
Does anybody know any solution?

[D1987]

As workaround I installed ingres via to a helm:
helm install stable/nginx-ingress --name my-nginx --set rbac.create=true

[aledbf]

Closing. This is fixed in master #4487
If you want to test the fix, you can use the image quay.io/kubernetes-ingress-controller/nginx-ingress-controller:dev