From ce316568c9c81b7c80777d5a32fe726604759987 Mon Sep 17 00:00:00 2001 From: "Chris S. Kim" Date: Tue, 9 Aug 2022 10:01:30 -0400 Subject: [PATCH] Update wording on intentions --- website/content/docs/connect/transparent-proxy.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/connect/transparent-proxy.mdx b/website/content/docs/connect/transparent-proxy.mdx index 93bbadb231..6e3353bbad 100644 --- a/website/content/docs/connect/transparent-proxy.mdx +++ b/website/content/docs/connect/transparent-proxy.mdx @@ -29,8 +29,8 @@ Without transparent proxy, application owners need to: With transparent proxy: -1. Upstreams are inferred from service intentions and/or imported services, - so no explicit configuration is needed. +1. Local upstreams are inferred from service intentions and peered upstreams are + inferred from imported services, so no explicit configuration is needed. 1. Outbound connections pointing to a KubeDNS name "just work" — network rules redirect them through the proxy. 1. Inbound traffic is forced to go through the proxy to prevent unauthorized