GCE L7 LB not picking up a custom readinessProbe URL

[Maykel Moya]

Hello

I'm trying to deploy a grafana instance inside Kubernetes (server 1.6.4) in GCE. I'm using the following manifests:

- Deployment: https://pastebin.com/HL5KqXtT

- Service: https://pastebin.com/jDQVj7aq

- Ingress: https://pastebin.com/3fR5udh6

It turns out that grafana serves a 302 on '/' but the default healthcheck expects a 200 on '/'. As you can see, there is a custom readinessProbe in the Deployment.

Once I post the previous resources to the kube-apiserver, everything is created as expected. Concretely, the Ingress gets a public ip4 but the healtcheck uses '/' instead of '/login' as path. In this state, I get a 502 if I curl the public ip4.

The problem is fixable by manually changing the probe path to '/login' in the GCE console.

Is this a bug or I'm missing something?

For reference:

- https://github.com/kubernetes/contrib/issues/1867

Regards,

maykel

[Nicks]

Hi Maykel,

The GCE ingress controller requires that you define the port (in your case 3000) within the Pod specification. For instance...

apiVersion: extensions/v1beta1

kind: Deployment

metadata:

  name: my-echo-deploy

spec:

  replicas: 1

  template:

    metadata:

      labels:

        app: echo

    spec:

      containers:

      - name: echoserver

        image: nicksardo/echoserver:latest

        ports:

        - name: http

          containerPort: 80

        - name: https

          containerPort: 443

        readinessProbe:

          httpGet:

            path: /healthcheck

            scheme: HTTP

            port: 80

[Maykel Moya]

On Friday, June 16, 2017 at 7:43:29 PM UTC+2, Nicks wrote:

Hi Maykel,

The GCE ingress controller requires that you define the port (in your case 3000) within the Pod specification. For instance...

That did the trick. Thanks!