Support sslSecretName/sslSecretNameInteral also for haproxy

[schegi]

Proposal

Currently usage of TSL with distinged certs for internal and external communication is only supported if proxysql is used as load balancing service. Support this also for the use of haproxy (add tls termination (external) to frontend and tls configuration (internal) to backend.

Use-Case

For managing cluster access with teleport, we need to set a distinged TLS cert set for external communication. Teleport defaults such cert wot server purpose, this again makes them useless for internal use (client purpose is also required).

Is this a feature you are interested in implementing yourself?

Maybe

Anything else?

No response