linkerd2/controller
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
..
api Remove the proxy-api container (#1813) 2018-10-29 16:31:43 -07:00
ca Add ServiceProfile support to k8s utilities (#1758) 2018-10-12 09:35:11 -07:00
cmd Remove the proxy-api container (#1813) 2018-10-29 16:31:43 -07:00
gen Add generated Kubernetes client for ServiceProfile custom resource (#1752) 2018-10-11 11:43:35 -07:00
k8s Add ServiceProfile support to k8s utilities (#1758) 2018-10-12 09:35:11 -07:00
proxy-injector Proxy injector must preserve the original pod template labels and annotations (#1765) 2018-10-16 15:30:45 -07:00
script/destination-client Remove the proxy-api container (#1813) 2018-10-29 16:31:43 -07:00
tap Fix integration test and docker build (#1790) 2018-10-19 10:23:34 -07:00
Dockerfile Send metric labels in profile API (#1800) 2018-10-29 14:28:09 -07:00