linkerd2/controller
Oliver Gould c5d3b281be
Add 100.64.0.0/10 to the set of discoverable networks (#5099)
It appears that Amazon can use the `100.64.0.0/10` network, which is
technically private, for a cluster's Pod network.

Wikipedia describes the network as:

> Shared address space for communications between a service provider
> and its subscribers when using a carrier-grade NAT.

In order to avoid requiring additional configuration on EKS clusters, we
should permit discovery for this network by default.
2020-10-19 12:59:44 -07:00
..
api Fix --all-namespaces flag handling (#5085) 2020-10-16 16:49:10 -04:00
cmd Remove dependency of linkerd-config for control plane components (#4915) 2020-10-06 22:19:18 +05:30
gen Remove dependency of linkerd-config for control plane components (#4915) 2020-10-06 22:19:18 +05:30
heartbeat Fix Heartbeat mem and cpu stats (#5042) 2020-10-08 16:31:16 -05:00
identity Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
k8s Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
proxy-injector Add 100.64.0.0/10 to the set of discoverable networks (#5099) 2020-10-19 12:59:44 -07:00
script/destination-client Print identity in destination client and fix proxy-identity log line (#4873) 2020-08-13 13:49:55 -07:00
service-mirror Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
sp-validator Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
tap Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
webhook Bump k8s client-go to v0.19.2 (#5002) 2020-09-28 12:45:18 -05:00
Dockerfile Build ARM docker images (#4794) 2020-08-05 11:14:01 -07:00