fix(meshpassthrough): disable tls and http inspector for mysql protocol #12839
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
When trying to communicate with MySQL, the user wants to enable communication with the database. Unfortunately, the MySQL protocol is slightly different, and the usual method of configuring filter chains does not work when using MeshPassthrough.
Implementation information
original_dst
listener filtermysql
which works only with CIDR/IP and requires port since we need to disabletls_inspector
andhttp_inspector
listener filters for the porttcp_proxy
but with with disabled listener filtersThe user may have rules with HTTP traffic and TCP traffic on the same port matching different IP. example: tls matching on port 8080(IP: 192.168.1.1) and TCP matching on 8080 (IP: 172.1.1.1), that would disable TLS inspector on the port 8080 and wouldn't match
Supporting documentation
https://dev.mysql.com/doc/dev/mysql-server/8.4.3/page_protocol_connection_phase_packets.html
envoyproxy/envoy#21044