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

Support ingress #48

Closed
tayzlor opened this issue Mar 22, 2016 · 10 comments
Closed

Support ingress #48

tayzlor opened this issue Mar 22, 2016 · 10 comments
Assignees

Comments

@tayzlor
Copy link
Member

tayzlor commented Mar 22, 2016

Would be good to have some out-of-the box options for Kubernetes Ingress controllers.

@enxebre
Copy link
Contributor

enxebre commented Mar 22, 2016

@wallies
Copy link
Contributor

wallies commented Mar 22, 2016

Needs to be more along the lines of https://github.com/nginxinc/kubernetes-ingress or even moving out to seperate machines for loadbalancing like http://www.devoperandi.com/load-balancing-in-kubernetes/

@enxebre
Copy link
Contributor

enxebre commented Mar 24, 2016

could put in place a pluggable fashion approach so user can choose at the time of deploying the platform

@olafmol
Copy link

olafmol commented Mar 29, 2016

@enxebre VAMP is very much about high-level "canary" patterns, providing f.e. specific percentages, NOT/AND/OR logic, conditions and filter-weights, to setup complex "buckets/segments" of visitors, and route them dynamically. We currently use HAproxy's to do this, but if Ingress provides the same feature-set as HAProxy ACL's we could integrate our VampGatewayAgents with Ingres instead of HAproxy.

@wallies
Copy link
Contributor

wallies commented Mar 29, 2016

@olafmol The way I see the community going is a lot of people will use the out of the box GCE or AWS loadbalancer but this offers very simple routing. Anything more complex I see them using Ingress and Ingress controllers. The Ingress controllers are pods that listens to the /ingresses endpoint to update itself and acts as a load balancer for Ingresses. It also listens on its assigned port for external requests. People have done examples running nginx ingress controllers and i have also seen haproxy and traefik ingress controllers. So this might be the way to go

@olafmol
Copy link

olafmol commented Mar 29, 2016

@wallies Yes, it would definately be feasible to integrate/extend Ingress with VAMP and use our VampGatewayAgents(VGA's)+HAProxy as Ingress-controllers. They are already designed to run in HA & high-performance setups, and support complex patterns like service-draining etc. This can also act as a service-loadbalancer while ingress is getting more mature. Would that make sense?

@tayzlor
Copy link
Member Author

tayzlor commented Apr 1, 2016

@sheerun
Copy link

sheerun commented Apr 13, 2016

Traefik is pending support for it: traefik/traefik#186

@errm
Copy link

errm commented Apr 15, 2016

We have been using this https://github.com/albertrdixon/romulus + vulcand for a while.

@enxebre enxebre self-assigned this May 31, 2016
@enxebre
Copy link
Contributor

enxebre commented Jun 2, 2016

Closing this as ce2a684 got in

Let's split the issue for the supported ingress
#106
#107

@enxebre enxebre closed this as completed Jun 2, 2016
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

No branches or pull requests

6 participants