Change configuring network topology from experimental to gatway; add note for envoyfilter section (#9556)

This commit is contained in:
jacob-delgado 2021-04-22 21:29:35 -06:00 committed by GitHub
parent b0f88378a1
commit 1627a1283e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions

View File

@ -1,6 +1,6 @@
---
title: Configuring Gateway Network Topology [Experimental]
description: How to configure gateway network topology (experimental).
title: Configuring Gateway Network Topology [Alpha]
description: How to configure gateway network topology (alpha).
weight: 60
keywords: [traffic-management,ingress,gateway]
owner: istio/wg-networking-maintainers
@ -9,8 +9,6 @@ test: yes
## Forwarding external client attributes (IP address, certificate info) to destination workloads
{{< boilerplate experimental >}}
Many applications require knowing the client IP address and certificate information of the originating request to behave
properly. Notable cases include logging and audit tools that require the client IP be populated and security tools,
such as Web Application Firewalls (WAF), that need this information to apply rule sets properly. The ability to
@ -201,6 +199,8 @@ for examples of using this capability.
## PROXY Protocol
{{< boilerplate experimental >}}
The [PROXY protocol](https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt) allows for exchanging and preservation of client attributes across multiple proxies without relying on Layer 7 protocols.
If your external load balancer is configured to use the PROXY protocol, the Istio gateway must also be configured to accept the PROXY protocol. Enabling this requires adding the [Envoy Proxy Protocol filter](https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/listener_filters/proxy_protocol) using an `EnvoyFilter` applied on the gateway workload. For example: