-
Notifications
You must be signed in to change notification settings - Fork 476
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
OpenFaaS does not work on a Istio enabled cluster #369
Comments
Fixed by #363 |
I'm having the exact problem described in the original post. I've verified that the Istio sidecar injection has been disabled according to the PR. My Environment
Please let me know if you need more information. I've currently got it working with |
Hi @lomeshpatel, As far as I am aware @stefanprodan runs Istio + OpenFaaS on his cluster, so I wouldn't expect any issues for you. You will need to create a new issue so that we gather everything we need from you. Alex |
Derek lock |
-- |
OpenFaaS installed with asyc enabled does not work with Istio.
Expected Behaviour
OpenFaaS should work with Istio v1.0.3 or newer.
Current Behaviour
OpenFaaS gateway, faas-idler and queue-worker are crashing at startup:
faas-idler logs:
gateway logs:
queue-worker logs:
When installing OpenFaaS with async off, the gateway starts but Prometheus can't scrape it using the SD discovery. Disabling the Istio sidecar for Prometheus fixes this.
nats://
is not supported by Envoy, so it must be disable nats-io/nats-operator#111Possible Solution
Disable Istio sidecar injection on NATS, prometheus, alertmanager and faas-idler see #363
Steps to Reproduce (for bugs)
Context
OpenFaaS was working with Istio see #279
Your Environment
GKE 1.11 with Istio add-on (1.0.3)
The text was updated successfully, but these errors were encountered: