You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, yes we need both because they install distinct products with distinct premises and requisites.
Maybe you meant if we really need to maintain both products, and yes we also need. HAProxy Ingress, the product behind this chart started 4 years ago (feb/2/17), this is one of the oldest ingress controllers out there. HAProxy Tech supported early versions of HAProxy Ingress, which was great, until they realized that they needed their own implementation. Maybe this question should be made on their tracker. Otoh HAProxy Ingress cannot and will not stop because we already use it on pretty large clusters, we depend on some hard to reproduce HAProxy Ingress' features and tunings, and we already have hundreds, maybe thousands of users - we don't track and, according to quay.io repository, we have about 100k downloads/day - and we respect all of them enough to simply leave them to their own luck.
Just to let you know this is a recurrent questions and I'm planning to blog about it. Feel free to ask if you have any doubt.
Hello guys -
Just curious if there is a reason to maintain both of these charts?
https://github.com/haproxytech/kubernetes-ingress
Cheers 😄
The text was updated successfully, but these errors were encountered: