Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You are absolutely right that getting traffic inside the cluster is probably one of most difficult tasks in Kubernetes. The standard ingress objects are too simple when you have a complex deployment. So, we wrote our own Ingress Third Party Resource to fit the needs of our deployment. We use HAProxy. We have been using this in prod for almost a year. You can find it here: https://github.com/appscode/voyager

If you find any issues or have questions, please file Github issues.



I found this last week and I'm very impressed because it solves a lot of the problems we had with existing ingresses.

I really like how you guys decided to do your own 3rd party manifests instead of using annotations.

I'm going to play more with this :-)


this is awesome!

please please submit this to kubernetes-incubator


Thanks for the kind words. The incubation process seemed too complicated (process heavy?) for small teams like us. But I will look into that again.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: