Readiness probe failed: HTTP probe failed with statuscode: 500 Back-off restarting failed container

12/1/2017

i used kubeadm to deploy my kubernetes dashboard... when i tried to deploy the nginx-ingress-controller in my dev namespace with default service-account...i am getting liveness probe and readiness failing with status code..

help me in this case.. i am using nginx-ingress-controller image is] gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.15

same error in test namespace also.... and in my logs its showing

 Received SIGTERM, shutting down
 shutting down controller queues
I1201 00:19:48.745970       7 nginx.go:237] stopping NGINX process...
I1201 00:19:48.746923       7 shared_informer.go:112] stop requested
E1201 00:19:48.746985       7 listers.go:63] Timed out waiting for caches to sync
[notice] 22#22: signal process started
 shutting down Ingress controller...
 Handled quit, awaiting pod deletion
I NGINX process has stopped
 Exiting with 0

why i am getting failing in cluster scope where i did wrong can anyone idea?

-- krish123
kubernetes-health-check

1 Answer

2/28/2018

You're most likely adding too little resources try removing the resources for debugging

-- Ami Mahloof
Source: StackOverflow