-
Notifications
You must be signed in to change notification settings - Fork 1.7k
GCE missing l7 ingress controller? #1733
Comments
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? |
Exactly. On Mon, Sep 12, 2016 at 9:45 AM, Matthew Fisher notifications@github.com
|
Thanks @thockin, shall I update the docs to reflect the changes? :) |
Aweome! On Mon, Sep 12, 2016 at 10:07 AM, Matthew Fisher notifications@github.com
|
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
Please send a pr that upates it to reflect that the L7 controller runs on the master. |
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:
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?
The text was updated successfully, but these errors were encountered: