Support routing incoming traffic to node-local services in k8s #659
Comments
This was referenced Sep 12, 2016
Merged
Tim-Brooks
pushed a commit
to Tim-Brooks/linkerd
that referenced
this issue
Dec 20, 2018
* fix pod status and count display in control plane dashboard section: - the control plane would show terminated and stale deployments in the UI, this is confusing and might indicate errors - this filters out temrinated and failed component deploys from the UI - it is to note that pending deploys will still be counted and represented with a greyed out status dot - Fixes: linkerd#606 Signed-off-by: Franziska von der Goltz <[email protected]> Signed-off-by: Franziska von der Goltz <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to support linkerd-to-linkerd when linkerd is running as daemonset, there must be a way for the incoming router of a daemonset linkerd to route traffic to the correct node-local service.
When the incoming router receives traffic, it should use the
io.l5d.headeridentifier to name the request based on thel5d-dst-conceteheader which was set by the outgoing router of the linkerd that sent the request. The list of service endpoints retrieved from service discovery should then be filtered down to only the endpoints which are on the same node as the linkerd. This can be done by selecting only the service endpoints on the same /24 subnet as the linkerd.This filtering is implemented as a NameTree transformer. Depends on #638 and #607
The text was updated successfully, but these errors were encountered: