linkerd2/controller/proxy-injector
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
..
fake multicluster: Use the proxy as an HTTP gateway (#4528) 2020-06-02 19:37:14 -07:00
metrics.go Instrumenting Proxy-Injector (#3354) 2019-09-20 09:46:57 -07:00
webhook.go cli: Add label selector flag for `stat` (#4040) 2020-02-17 13:40:07 -05:00
webhook_ops.go Add validation webhook for service profiles (#2623) 2019-04-05 16:10:47 -05:00
webhook_test.go Add destination-get-networks option (#4608) 2020-06-18 20:07:47 +03:00