linkerd2/proxy-init
Alex Leong 5b054785e5
Read service profiles from client or server namespace instead of control namespace (#2200)
Fixes #2077 

When looking up service profiles, Linkerd always looks for the service profile objects in the Linkerd control namespace.  This is limiting because service owners who wish to create service profiles may not have write access to the Linkerd control namespace.

Instead, we have the control plane look for the service profile in both the client namespace (as read from the proxy's `proxy_id` field from the GetProfiles request and from the service's namespace.  If a service profile exists in both namespaces, the client namespace takes priority.  In this way, clients may override the behavior dictated by the service.

Signed-off-by: Alex Leong <alex@buoyant.io>
2019-02-07 14:51:43 -08:00
..
cmd WIP: CNI Plugin (#2071) 2019-01-30 11:51:34 -08:00
integration_test Fix most golint issues that are not comment related (#1982) 2018-12-20 10:37:47 -08:00
iptables WIP: CNI Plugin (#2071) 2019-01-30 11:51:34 -08:00
Dockerfile Read service profiles from client or server namespace instead of control namespace (#2200) 2019-02-07 14:51:43 -08:00
main.go Send non-zero status code when proxy-init command fails (#2064) 2019-01-10 15:48:42 -08:00