mirror of https://github.com/linkerd/linkerd2.git
71ce786dd3
Up until now, the proxy-api controller service has been the sole service that the proxy communicates with, implementing the majoriry of the API defined in the `linkerd2-proxy-api` repo. But this is about to change: linkerd/linkerd2-proxy-api#25 introduces a new Identity service; and this service must be served outside of the existing proxy-api service in the linkerd-controller deployment (so that it may run under a distinct service account). With this change, the "proxy-api" name becomes less descriptive. It's no longer "the service that serves the API for the proxy," it's "the service that serves the Destination API to the proxy." Therefore, it seems best to bite the bullet and rename this to be the "destination" service (i.e. because it only serves the `io.linkerd.proxy.destination.Destination` service). Co-authored-by: Kevin Lingerfelt <kl@buoyant.io> Signed-off-by: Kevin Lingerfelt <kl@buoyant.io> |
||
|---|---|---|
| .. | ||
| config-linkerd-secrets.yaml | ||
| config-linkerd-trust-anchors.yaml | ||
| config-proxy-init.yaml | ||
| config-proxy-tls-disabled.yaml | ||
| config-proxy.yaml | ||
| deployment-inject-disabled.yaml | ||
| deployment-inject-empty.yaml | ||
| deployment-inject-enabled.yaml | ||
| deployment-with-injected-proxy.yaml | ||
| inject-init-container-spec.yaml | ||
| inject-linkerd-secrets-volume-spec.yaml | ||
| inject-sidecar-container-spec.yaml | ||
| inject-trust-anchors-volume-spec.yaml | ||
| namespace-inject-disabled.yaml | ||
| namespace-inject-enabled.yaml | ||