consul/website/content
Freddy 4a4a1ebff8 Only consider virtual IPs for transparent proxies (#10162)
Initially we were loading every potential upstream address into Envoy
and then routing traffic to the logical upstream service. The downside
of this behavior is that traffic meant to go to a specific instance
would be load balanced across ALL instances.

Traffic to specific instance IPs should be forwarded to the original
destination and if it's a destination in the mesh then we should ensure
the appropriate certificates are used.

This PR makes transparent proxying a Kubernetes-only feature for now
since support for other environments requires generating virtual IPs,
and Consul does not do that at the moment.
2021-05-03 15:06:36 -06:00
..
api-docs Merge pull request #10112 from hashicorp/dnephin/remove-streaming-from-cache 2021-04-28 21:58:32 +00:00
commands connect: update supported envoy versions to 1.18.2, 1.17.2, 1.16.3, and 1.15.4 (#10101) 2021-04-29 20:22:41 +00:00
docs Only consider virtual IPs for transparent proxies (#10162) 2021-05-03 15:06:36 -06:00
partials maintenance complete, pending markdown-page component addition 2020-12-16 16:55:23 -05:00
security.mdx maintenance complete, pending markdown-page component addition 2020-12-16 16:55:23 -05:00