connect: Fix comment DYNAMIC_DNS to LOGICAL_DNS (#4799)

LOGICAL_DNS is one of the supported service discovery types [1].

[1] https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/service_discovery#arch-overview-service-discovery-types
This commit is contained in:
Dhi Aurrahman 2018-10-24 21:02:01 +07:00 committed by Hans Hasselberg
parent 9819683653
commit 649082ab35
1 changed files with 1 additions and 1 deletions

View File

@ -213,7 +213,7 @@ func (c *cmd) templateArgs() (*templateArgs, error) {
} }
// We use STATIC for agent which means we need to resolve DNS names like // We use STATIC for agent which means we need to resolve DNS names like
// `localhost` ourselves. We could use STRICT_DNS or DYNAMIC_DNS with envoy // `localhost` ourselves. We could use STRICT_DNS or LOGICAL_DNS with envoy
// but Envoy resolves `localhost` differently to go on macOS at least which // but Envoy resolves `localhost` differently to go on macOS at least which
// causes paper cuts like default dev agent (which binds specifically to // causes paper cuts like default dev agent (which binds specifically to
// 127.0.0.1) isn't reachable since Envoy resolves localhost to `[::]` and // 127.0.0.1) isn't reachable since Envoy resolves localhost to `[::]` and