linkerd2/pkg/charts
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
..
cni bin/helm-build automatically updates version in values.yaml (#4058) 2020-02-18 11:19:58 -05:00
linkerd2 Add destination-get-networks option (#4608) 2020-06-18 20:07:47 +03:00
multicluster add installNamespace flag to Go (#4539) 2020-06-03 17:19:49 +03:00
static Refactor proxy injection to use Helm charts (#3200) 2019-08-07 17:32:37 -05:00
charts.go Refactor linkerd-config-addons configmap (#4318) 2020-05-05 14:11:21 +05:30