-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGSEGV exception in glbc #1112
Comments
Also, a question: do I even have to run Per tutorial in that readme, it seems like running |
@gmile You don't need to run that command. GKE already runs the ingress controller on the master - though, you can't see it via However, this does expose a bug for those running this controller on an unmanaged cluster without a GCE configuration file. The controller should gracefully handle no configuration provided. |
These docs are more helpful for GKE: |
@nicksardo do you think the documentation could be updated with a note pointing, once again, that in case of GKE, there's no need to create the controller? |
I'm using GKE with Kubernetes. Master is 1.6.7, nodes are 1.6.4.
After following instruction from readme here, the ingress is working fine, which is indicated by the following:
However this is what I see in the logs for
l7-lb-controller
:Running:
Reveals the following, with the last 3 lines repeating over and over again (removed for brevity):
Filing the bug in case that exception should not happen, and needs to be fixed.
The text was updated successfully, but these errors were encountered: