Hey Willy

On 20/03/2020 12:02, Willy Tarreau wrote:
> Hi Moemen,
> On Thu, Mar 19, 2020 at 06:47:42PM +0100, Moemen MHEDHBI wrote:
>> This ML is the right place to contribute to the HAProxy software, but
>> for the ingress controller better do this by creating an issue in the
>> github project.
>> It isn't your fault anyway, we have updated the contribute/discussion
>> sections of the README in order to put clear information.
> Please note that eventhough a number of us don't really understand the
> details in all of this, I'm pretty sure that another large part is very
> much interested in following such proposals, and there's more real users
> exposure here than in an issue tracker (which is also why we automatically
> forward the pull requests here). So as long as these ones do not represent
> 80% of the traffic here, I think it's fine and beneficial to let
> contributors share their thoughts here, even if the controller technically
> is a distinct project. But I could be wrong and if some people disagree
> with me, do not hesitate to blame me.
> Cheers
> Willy

Since we handle contributions via github pull requests (for tracking,
referencing, searching purposes), I thought in the first place that we
better avoid having same discussion scattered on different places.

I think that if we have all ingress controller discussion here this will
probably bring noise regarding HAProxy being the main subject of the ML.
In the other hand preventing any controller related discussion here is
counterproductive, so in my opinion any features/contributions to the
controller that also deals closely with HAProxy are probably better
discussed here.

Regarding what David is talking about, this is mostly related to
Kubernetes internals (pods, annotations, Endpoints, etc) that's why I
suggested we talk about this in github where other similar discussions
take place. But I may be wrong and among this ML there may be people
that have something to say about this post in this case of course they
should feel free to answer here.


Reply via email to