Which operator(s) is this request for?
Why this matters
For organizations subject to compliance frameworks such as PCI-DSS, HIPAA, or SOC 2, accurate client IP attribution in database audit logs is not optional. It is a hard requirement for forensic investigation and access reviews. Without PROXY protocol support in ProxySQL, all database activity appears to originate from ProxySQL's pod IP, rendering audit trails incomplete and IP-based access controls ineffective. Bringing ProxySQL to parity with the operator's existing HAProxy PROXY protocol support ensures that teams can choose their preferred proxy layer without sacrificing visibility, security posture, or compliance readiness.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1557
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Which operator(s) is this request for?
Why this matters
For organizations subject to compliance frameworks such as PCI-DSS, HIPAA, or SOC 2, accurate client IP attribution in database audit logs is not optional. It is a hard requirement for forensic investigation and access reviews. Without PROXY protocol support in ProxySQL, all database activity appears to originate from ProxySQL's pod IP, rendering audit trails incomplete and IP-based access controls ineffective. Bringing ProxySQL to parity with the operator's existing HAProxy PROXY protocol support ensures that teams can choose their preferred proxy layer without sacrificing visibility, security posture, or compliance readiness.
Jira: https://perconadev.atlassian.net/browse/K8SPXC-1557
Community Note