mirror of https://github.com/linkerd/linkerd2.git
7f3d872930
In #4585 we are observing an issue where a loop is encountered when using nginx ingress. The problem is that the outbound proxy does a dst lookup on the IP address which happens to be the very same address the ingress is listening on. In order to avoid situations like that this PR introduces a way to modify the set of networks for which the proxy shall do IP based discovery. The change introduces a helm flag `.Values.global.proxy.destinationGetNetworks` that can be used to modify this value. There are two ways a user can affect the this setting: - setting the `destinationGetNetworks` field in values during a Helm install, which changes the default on all injected pods - using an annotation ` config.linkerd.io/proxy-destination-get-networks` for injected workloads to override this value Note that this setting cannot be tweaked through the `install` or `inject` command Fix: #4585 Signed-off-by: Zahari Dichev <zaharidichev@gmail.com> |
||
|---|---|---|
| .. | ||
| add-ons | ||
| linkerd2 | ||
| linkerd2-cni | ||
| linkerd2-multicluster | ||
| partials | ||
| patch | ||