GLBC on Google Container Engine

[Andy Hume]

Hi,

Based on various documentation I expected to see the l7-lb-controller on my cluster, in this list. But I cannot. Is that a recent change to GKE? It means I can't see logs for the controller.

$ kubectl get pods --namespace=kube-system

NAME                                                           READY     STATUS    RESTARTS   AGE

fluentd-cloud-logging-gke-flags-4-default-pool-69d0cbbb-jha4   1/1       Running   0          2h

fluentd-cloud-logging-gke-flags-4-default-pool-a31c4c33-0q2m   1/1       Running   0          2h

fluentd-cloud-logging-gke-flags-4-default-pool-ed6ee4c0-r991   1/1       Running   0          2h

heapster-v1.1.0-507289059-o73cs                                2/2       Running   0          2h

kube-dns-v17.1-d4emf                                           3/3       Running   0          2h

kube-dns-v17.1-nlc4w                                           3/3       Running   0          2h

kube-proxy-gke-flags-4-default-pool-69d0cbbb-jha4              1/1       Running   0          2h

kube-proxy-gke-flags-4-default-pool-a31c4c33-0q2m              1/1       Running   0          2h

kube-proxy-gke-flags-4-default-pool-ed6ee4c0-r991              1/1       Running   0          2h

kubernetes-dashboard-v1.1.1-4u0fb                              1/1       Running   0          2h

l7-default-backend-v1.0-mmcwa                                  1/1       Running   0          2h

Secondly, is there a way of configuring health checks for the add-on load balancer? I believe it defaults to checking for a 200 response from /, but my application serves a 404 at that endpoint.

Thanks,

Andy.

[Robert Bailey]

What version of Kubernetes are you running? Starting with version 1.3, the L7 load balancer addon is no longer running on your nodes (and visible as a pod) but it is still running and acting on ingress objects. 

--
You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

[Prashanth B]

On Friday, September 2, 2016 at 6:36:31 AM UTC-7, Andy Hume wrote:

Hi,

Based on various documentation I expected to see the l7-lb-controller on my cluster, in this list. But I cannot. Is that a recent change to GKE? It means I can't see logs for the controller.

$ kubectl get pods --namespace=kube-system

NAME                                                           READY     STATUS    RESTARTS   AGE

fluentd-cloud-logging-gke-flags-4-default-pool-69d0cbbb-jha4   1/1       Running   0          2h

fluentd-cloud-logging-gke-flags-4-default-pool-a31c4c33-0q2m   1/1       Running   0          2h

fluentd-cloud-logging-gke-flags-4-default-pool-ed6ee4c0-r991   1/1       Running   0          2h

heapster-v1.1.0-507289059-o73cs                                2/2       Running   0          2h

kube-dns-v17.1-d4emf                                           3/3       Running   0          2h

kube-dns-v17.1-nlc4w                                           3/3       Running   0          2h

kube-proxy-gke-flags-4-default-pool-69d0cbbb-jha4              1/1       Running   0          2h

kube-proxy-gke-flags-4-default-pool-a31c4c33-0q2m              1/1       Running   0          2h

kube-proxy-gke-flags-4-default-pool-ed6ee4c0-r991              1/1       Running   0          2h

kubernetes-dashboard-v1.1.1-4u0fb                              1/1       Running   0          2h

l7-default-backend-v1.0-mmcwa                                  1/1       Running   0          2h

As Robert mentioned, it's running on the master for versions >= 1.3, so just like the other master components you can't see its logs. 

On the flip side, it's now managed on the GKE master, so it doesn't consume node resources. 

You should be able to get all the information you need by running `kubectl describe` on the ingress. Please report clarity issues on: https://github.com/kubernetes/contrib/issues/1369

 

Secondly, is there a way of configuring health checks for the add-on load balancer? I believe it defaults to checking for a 200 response from /, but my application serves a 404 at that endpoint.

Relevant documentation: https://github.com/kubernetes/contrib/tree/master/ingress/controllers/gce#health-checks

Example: https://github.com/kubernetes/contrib/tree/master/ingress/controllers/gce/examples/health_checks

 

Thanks,

Andy.