Try to understand the mode for tcpcr in 3.0.0

[cxfcxf]

https://github.com/haproxytech/kubernetes-ingress/blob/master/pkg/handler/tcp-cr.go#L139
in this code, it forces the frontend to have mode tcp

but in the TCP CR doc here

it is said to allow mode http or tcp in CRD. i am confused here, is that http for something else or its just not implanted?

[hdurand0710]

@cxfcxf ,
You are right. We will update the documentation accordingly.
You can use all fields of a client native Frontend model, expect the mode that is forced to tcp.
The documentation here was auto generated from the Backend model, we should explain that mode is not used and if used would we forced to tcp.

[cxfcxf]

thanks, i m also wondering if there is a plan to support more bind params in http/https handler?

we try to split thread for http and https works, but it seems its not supported.

[cxfcxf]

so i sent a PR for the supporting thread pin on http https and healthz which can be helpful for people runnign it as external mode

#661

[oktalz]

thanks, i m also wondering if there is a plan to support more bind params in http/https handler?

yes, ideally we end up with a frontend CRD completely, its in plans

[stale]

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.