linkerd2

Commit Graph

Author	SHA1	Message	Date
Radu M	07cbfe2725	Fix most golint issues that are not comment related (#1982 ) Signed-off-by: Radu Matei <radu@radu-matei.com>	2018-12-20 10:37:47 -08:00
Kevin Lingerfelt	86e95b7ad3	Disable serivce profiles in single-namespace mode (#1980 ) Signed-off-by: Kevin Lingerfelt <kl@buoyant.io>	2018-12-13 14:37:18 -08:00
Alex Leong	cbb196066f	Support service profiles for external authorities (#1928 ) Add support for service profiles created on external (non-service) authorities. For example, this allows you to create a service profile named `linkerd.io` which will apply to calls made to `linkerd.io`. This is done by changing the `LINKERD2_PROXY_DESTINATION_PROFILE_SUFFIXES` to `.` so that the proxy will attempt to lookup a service profile for any authority. We provide the `--disable-external-profiles` proxy flag to revert this behavior in case it is a problem. We also refactor the proxy-api implementation of GetProfiles so that it does the profile lookup, regardless of if the authority looks like a Kubernetes service name or not. To simplify this, support for multiple resolves (which was unused) was removed. Signed-off-by: Alex Leong <alex@buoyant.io>	2018-12-05 14:32:59 -08:00
Alex Leong	d8b5ebaa6d	Remove the proxy-api container (#1813 ) A container called `proxy-api` runs in the Linkerd2 controller pod. This container listens on port 8086 and serves the proxy-api but does nothing other than forward gRPC requests to the destination container which listens on port 8089. We remove the proxy-api container altogether and change the destination container to listen on port 8086 instead of 8089. The result is that clients still use the proxy-api by connecting to `proxy-api.<ns>.svc.cluster.local:8086` but the controller has one fewer containers. This results in a simpler system that is easier to reason about. Signed-off-by: Alex Leong <alex@buoyant.io>	2018-10-29 16:31:43 -07:00

4 Commits