Skip to content
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

[Feature] Gateway bypass #19

Closed
alexellis opened this issue Jan 14, 2020 · 0 comments · Fixed by #24
Closed

[Feature] Gateway bypass #19

alexellis opened this issue Jan 14, 2020 · 0 comments · Fixed by #24

Comments

@alexellis
Copy link
Member

alexellis commented Jan 14, 2020

Expected Behaviour

This feature would allow an Ingress record to be created that bypasses the gateway, so that an endpoint can be accessed with absolute minimal latency, by removing an additional hop.

Caveats

Today the IngressOperator, FNI definitions are created in the openfaas namespace which causes an Ingress record to be created in the openfaas namespace pointing at the gateway, which is also deployed in that namespace.

For a bypass mode we will have to deploy all resources a second time into the openfaas-fn namespace because Ingress cannot point into a different namespace - i.e. having an Ingress in openfaas which connects to a service in openfaas-fn. It only works in the first example because the gateway acts as a proxy.

See also: kubernetes/kubernetes#17088

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

Successfully merging a pull request may close this issue.

1 participant