docs: Update MySQL Server Version#24517
Conversation
smallinsky
force-pushed
the
smallinsky/proxy_mysql_engine_version_docs
branch
2 times, most recently
from
b306c81 to
e7e338f
Compare
smallinsky
force-pushed
the
smallinsky/proxy_mysql_engine_version_docs
branch
from
e7e338f to
785f7bb
Compare
| access see the [RBAC](../database-access/rbac.mdx) documentation. | ||
|
|
||
| ## Connection to MySQL database results in "Unknown system variable 'query_cache_size'" error | ||
| When a Teleport Proxy is configured with Teleport Proxy Listener Mode (`proxy_listener_mode: separate`) by default MySQL client connections to the Teleport Proxy don't use the TLS Routing feature that allows propagating correct MySQL Server Version. |
There was a problem hiding this comment.
I think the structure of this sentence pretty ambiguous. Does this mean that TLS Routing allows propagating the correct MySQL server version, or that, by not using TLS Routing, the Proxy Service can propagate the correct version?
There was a problem hiding this comment.
@ptgott
Yes, With TLS Routing enabled the MySQL Engine version propagation works correctly and this issue occurs only for setups where TLS Routing is disabled.
I have rephrased this sentence to:
When TLS Routing feature is disable by default, the Teleport Proxy Service returns
8.0.0-Teleportas the MySQL server version. In some cases, like connecting with a GUI Client, this can result in obtaining anUnknown system variable 'query_cache_size'error that indicates that MySQL capabilities were not properly negotiated between the MySQL client and server.
smallinsky
force-pushed
the
smallinsky/proxy_mysql_engine_version_docs
branch
from
be3bc57 to
b3e7e23
Compare
|
@smallinsky See the table below for backport results.
|
4 participants
What