Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

GCE missing l7 ingress controller? #1733

Closed
bacongobbler opened this issue Sep 12, 2016 · 5 comments
Closed

GCE missing l7 ingress controller? #1733

bacongobbler opened this issue Sep 12, 2016 · 5 comments

Comments

@bacongobbler
Copy link

Right now if you deploy or upgrade a GCE cluster to 1.3.6, the l7 ingress controller that is mentioned in http://kubernetes.io/docs/user-guide/ingress/#prerequisites is not present, but instead you get:

$ kubectl get pods --namespace=kube-system -l k8s-app=glbc
NAME                            READY     STATUS    RESTARTS   AGE
l7-default-backend-v1.0-bym3n   1/1       Running   0          3d

This is not mentioned anywhere in the GCE release notes. Is this an unintentional bug in GCE or are the docs out of date and the ingress controller is held elsewhere?

@bacongobbler bacongobbler changed the title GCE missing l7 ingress controller GCE missing l7 ingress controller? Sep 12, 2016
@bacongobbler
Copy link
Author

Looking at the differences closer, it seems like only the glbc image is missing by default. When I dump l7-default-backend-v1.0 on a fresh cluster, I see the following: https://gist.github.com/bacongobbler/5464eec6e8d5e799945528f5e0b4a362

Is the glbc now managed by GCE or something?

@thockin
Copy link
Contributor

thockin commented Sep 12, 2016

Exactly.

On Mon, Sep 12, 2016 at 9:45 AM, Matthew Fisher notifications@github.com
wrote:

Looking at the differences closer, it seems like only the glbc image
https://github.com/kubernetes/contrib/blob/186beffac4ca5083dfd14215fbb7b85eba404e8f/ingress/controllers/gce/rc.yaml#L64-L82
is missing by default. When I dump l7-default-backend-v1.0 on a fresh
cluster, I see the following: https://gist.github.com/bacongobbler/
5464eec6e8d5e799945528f5e0b4a362

Is the glbc now managed by GCE or something?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1733 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVIfzxYC4teUg-Jege3ZZEUSisk_Yks5qpYGZgaJpZM4J6s7Q
.

@bacongobbler
Copy link
Author

Thanks @thockin, shall I update the docs to reflect the changes? :)

@thockin
Copy link
Contributor

thockin commented Sep 12, 2016

Aweome!

@bprashanth

On Mon, Sep 12, 2016 at 10:07 AM, Matthew Fisher notifications@github.com
wrote:

Thanks @thockin https://github.com/thockin, shall I update the docs to
reflect the changes? :)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1733 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVHQ3eJz16dZUNAOMENbXIeYgWhPkks5qpYbqgaJpZM4J6s7Q
.

@bprashanth
Copy link

sorry for the confusion, this happened in 1.3.0 itself (see Highlights section of https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md/#highlights).

This line is inaccurate

On GCE/GKE there should be a L7 cluster addon, deployed into the kube-system namespace:

Please send a pr that upates it to reflect that the L7 controller runs on the master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants