Clarify positioning of haproxy ingress vs new unified product?

[franklouwers]

With the recent announcement of the new "Unified" product, what's the positioning and roadmap of this project? Will both merge? Will they remain separate? If so, what's the roadmap?

The not-so-sudden-but-still-sudden announcement that ingress-nginx is now officially death, choices need to be made in a lot of teams, and clarification of all the options would greatly help ...

[oktalz]

hi @franklouwers,

they will not merge, they will keep being separate.

haproxy-unified-gateway will get support for handling ingress objects, though in a bit different way (this project has huge amount of annotations, where HUG will have more focus on CRDs).

HUG is currently in beta state, since it does not yet support most of Gateway API objects.

That being said, ingress controller will remain to be maintained for a while (3.2 version was a bit delayed, but release will happen).

For how long Ingress controller will be developed, it is hard to say, but deprecation of Ingress API was not mentioned.
What I can tell you is: when we release 3.2 that means at least one year of full support (for Enterprise version its longer but that is irrelevant here)

[franklouwers]

Thanks for clarifying! Might be good to add that to (both) README(s)