title: Readiness probe failed: HTTP probe failed with statuscode: 500 Back-off restarting failed container
body: <p>I used kubeadm to deploy my Kubernetes dashboard.
  When I tried to deploy the <em>nginx-ingress-controller</em> in my dev namespace with default service-account, I was getting <em>liveness probe</em> and readiness failing with status code.</p>
  <p>nginx-ingress-controller image is</p>
  <pre><code>gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.15
  </code></pre>
  <p>I get the same error in the test namespace also.
  In my logs it's showing</p>
  <pre><code> 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
  </code></pre>
  <p>Why am I getting failures in cluster scope; where is my failure?</p>