mirror of https://github.com/linkerd/linkerd2.git
649e784d9c
* Temporarily stop trying to support configurable zones in the proxy. None of the zone configuration is tested and lots of things assume the cluster zone is `cluster.local`. Further, how exactly the proxy will actually learn the cluster zone hasn't been decided yet. Just hard-code the zone as "cluster.local" in the proxy until configurable zones are fully implemented and tested to be working correctly. Signed-off-by: Brian Smith <brian@briansmith.org> * Remove the CONDUIT_PROXY_DESTINATIONS_AUTOCOMPLETE_FQDN setting The way that Kubernetes configures DNS search suffixes has some negative consequences as some names like "example.com" are ambiguous: depending on whether there is a service "example" in the "com" namespace, "example.com" may refer to an external service or an internal service, and this can fluctuate over time. In recognition of that we added the CONDUIT_PROXY_DESTINATIONS_AUTOCOMPLETE_FQDN setting, thinking this would be part of a solution for users to opt out of the unfortunate behavior if their applications didn't depend on the DNS search suffix feature. It turns out similar effects can be acheived using a custom dnsConfig, starting in Kubernetes 1.10 when dnsConfig reaches the beta stability level. Now any CONDUIT_PROXY_DESTINATIONS_AUTOCOMPLETE_FQDN-based seems duplicative. Further, attempting to support it optionally made the code complex and hard to read. Therefore, let's just remove it. If/when somebody actually requests this functionality then we can add it back, if dnsConfig isn't a valid alternative for them. Signed-off-by: Brian Smith <brian@briansmith.org> * Further hard-code "cluster.local" as the zone, temporarily. Addresses review feedback. Signed-off-by: Brian Smith <brian@briansmith.org> |
||
|---|---|---|
| .. | ||
| client.rs | ||
| controller.rs | ||
| mod.rs | ||
| proxy.rs | ||
| server.rs | ||
| tcp.rs | ||