Ingress reports unhealthy backend

11/17/2016

I'm using GCE with Kubernetes to host my rails app but the ingress reports the pod as UNHEALTHY. Below is my setup

Ingress:

spec:
  backend:
    serviceName: my-service
    servicePort: 80

Service:

spec:
  type: NodePort
  selector:
    app: my-app
  ports:
    - port: 80 
      targetPort: 3000

Depoyment

readinessProbe:
  httpGet:
    path: /health_check
    port: 3000
    initialDelaySeconds: 20
    timeoutSeconds: 5

The ingress reports the pod as UNHEALTHY and I don't see /health_check shows up in the health checks list in GCE console. It seems it's not picked up by Google load balancer controller.

Thank you very much.

-- ldo
google-compute-engine
kubernetes
kubernetes-health-check

1 Answer

11/18/2016

It turned out the ingress didn't pick up the new path of the readiness probe that I changed earlier. The problem was solved after I recreated the ingress (which was definitely not an optimal solution).

-- ldo
Source: StackOverflow