|
|
|
@ -29,8 +29,8 @@ Without transparent proxy, application owners need to:
|
|
|
|
|
|
|
|
|
|
|
|
With transparent proxy:
|
|
|
|
With transparent proxy:
|
|
|
|
|
|
|
|
|
|
|
|
1. Upstreams are inferred from service intentions and/or imported services,
|
|
|
|
1. Local upstreams are inferred from service intentions and peered upstreams are
|
|
|
|
so no explicit configuration is needed.
|
|
|
|
inferred from imported services, so no explicit configuration is needed.
|
|
|
|
1. Outbound connections pointing to a KubeDNS name "just work" — network rules
|
|
|
|
1. Outbound connections pointing to a KubeDNS name "just work" — network rules
|
|
|
|
redirect them through the proxy.
|
|
|
|
redirect them through the proxy.
|
|
|
|
1. Inbound traffic is forced to go through the proxy to prevent unauthorized
|
|
|
|
1. Inbound traffic is forced to go through the proxy to prevent unauthorized
|
|
|
|
|
Chris S. Kim
2 years ago