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
..
api_handlers.go	Update Top Routes in dashboard to use new API, add `to` query options (#2112)	2019-01-23 14:29:27 -08:00
api_handlers_test.go	Fix most golint issues that are not comment related (#1982)	2018-12-20 10:37:47 -08:00
grafana_proxy.go	Proxy grafana requests through web service (#2039)	2019-01-04 16:07:57 -08:00
handlers.go	Read service profiles from client or server namespace instead of control namespace (#2200)	2019-02-07 14:51:43 -08:00
handlers_test.go	Read service profiles from client or server namespace instead of control namespace (#2200)	2019-02-07 14:51:43 -08:00
server.go	Wire up stats commands for daemonsets (#2006) (#2086)	2019-01-24 14:34:13 -08:00
test_helpers.go	Enable lint check for comments (#2023)	2019-01-02 14:03:59 -08:00