Bug: HostEnvVar should be 127.0.0.1, not localhost #124
Assignees
Labels
priority: p0
Highest priority. Critical issue. P0 implies highest priority.
Comments
hessjcg
added
the
priority: p0
hessjcg
added a commit
that referenced
this issue
Dec 6, 2022
hessjcg
added a commit
that referenced
this issue
Dec 7, 2022
When a proxy is configured to serve a TCP connection, the application connecting must use the loopback interface's ip4 address explicitly: 127.0.0.1 instead of the symbolic name localhost because localhost is interpreted differently by different database client libraries. Using 127.0.0.1 instead avoids this ambiguity. Fixes #124
This was referenced Dec 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
When the HostEnvName field is set on a InstanceSpec, it should set an environment variable on the workload pods
with the value
127.0.0.1.Actual Behavior
Instead it sets it to
localhostwhich is problematic for the mysql command line tool. Mysql assumes localhost means "a local socket connection" while127.0.0.1is unambiguously a tcp connection.The text was updated successfully, but these errors were encountered: