linkerd2/cli
Zahari Dichev 7f3d872930
Add destination-get-networks option (#4608)
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>
2020-06-18 20:07:47 +03:00
..
cmd Add destination-get-networks option (#4608) 2020-06-18 20:07:47 +03:00
installsp Fixed prom route in linkerd service profile, and some extra cleanup (#4493) 2020-06-03 12:53:50 -05:00
table Add linkerd alpha stat command (#4130) 2020-03-05 15:23:14 -08:00
Dockerfile-bin Add --close-wait-timeout inject flag (#4409) 2020-05-21 14:14:14 -07:00
main.go Refactor proxy injection to use Helm charts (#3200) 2019-08-07 17:32:37 -05:00