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

Why 2 HAProxy k8s ingress controller projects? #272

Closed
mecampbellsoup opened this issue Jan 26, 2021 · 5 comments
Closed

Why 2 HAProxy k8s ingress controller projects? #272

mecampbellsoup opened this issue Jan 26, 2021 · 5 comments
Labels

Comments

@mecampbellsoup
Copy link

Hi guys -

We are looking at different API gateway solutions for a project we are embarking on.

We wanted to see what HAProxy-as-k8s-ingress options were out there, and immediately you see that in addition to this project there is another:

https://github.com/haproxy-ingress/charts

I asked the other project for a little context on why such a split existed in the community (as compared to e.g. the NGINX/OpenResty gateway people which have all coalesced around Kong), but I was curious to see your perspective on it.

  • Are there important differences that potential new users like us should be aware of starting out?
  • Is documentation significantly better/worse?
  • etc.

Thanks for your help in evaluating our options here.

@daniel-corbett
Copy link
Contributor

Hello 👋, HAProxy Technologies made significant contributions to the jcmoraisjr/haproxy-ingress project, including the use of the Runtime API and DNS for Service Discovery. We saw a demand from our users for an Ingress Controller that we were authoritative on and could address extreme performance requirements. For example, one user was having scaling issues when using the jcmoraisjr/haproxy-ingress project when dealing with thousands of ingress resources, which we had solved due to different architecture decisions within our own implementation. We also need to be able to cater to the needs of our enterprise customers and offer an Ingress Controller that could be extended to support HAProxy Enterprise native modules and enterprise specific features without putting the burden on the community contributors and maintainers. We believe there's room for both options to exist harmoniously and are really happy that multiple solutions exist as it shows the power of open source (and the power of HAProxy 😊 ) and having a diversity of projects is only to the benefit of the overall community.

@kowshikn
Copy link

@daniel-corbett Hello, can you share more details about the scaling issue. I am in particular interested to know about any benchmark or production systems that have used haproxytech/kubernetes-ingress with multiple ingress resources. I have a usecase where we will be running multiple ingress resources(about thousand) with high throughput. Would be great if you can share more details about it.

@bluebrown
Copy link
Contributor

But what is the actual difference?

@mecampbellsoup
Copy link
Author

But what is the actual difference?

Read the maintainer's response here.

@stale
Copy link

stale bot commented Jan 3, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 3, 2022
@stale stale bot closed this as completed Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants