linkerd2/controller/destination
Andrew Seigner 9e8cce0838
Destination service returns "Running" pod labels (#781)
When the Destination sees an IP address, it looks up Pods by that IP,
and associates Pod label data to it. If the lookup by IP returned more
than one Pod, it simply picked the first one. This is not correct,
specifically in cases where one pod is in a Running state, and others
are not.

Modify the Destination service to only return label data for Pods in the
Running state.

Fixes #773

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
2018-04-17 14:42:54 -07:00
..
client.go Introducing Conduit, the ultralight service mesh 2017-12-05 00:24:55 +00:00
dns.go Refactor destination service and add tests in preparation to add information about labels (#645) 2018-03-30 11:36:48 -07:00
dns_test.go Fix flakey dns_test (#516) 2018-03-05 16:50:33 -08:00
k8s_resolver.go Controller: add more destination labels, fix service label (#731) 2018-04-11 10:44:52 -07:00
k8s_resolver_test.go Controller: add more destination labels, fix service label (#731) 2018-04-11 10:44:52 -07:00
listener.go Destination service returns "Running" pod labels (#781) 2018-04-17 14:42:54 -07:00
listener_test.go Destination service returns "Running" pod labels (#781) 2018-04-17 14:42:54 -07:00
resolver.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
resolver_test.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
server.go Controller: add more destination labels, fix service label (#731) 2018-04-11 10:44:52 -07:00
server_test.go Add pod-based metric_labels to destinations response (#429) (#654) 2018-04-02 18:36:57 -07:00
test_helper.go Controller: add more destination labels, fix service label (#731) 2018-04-11 10:44:52 -07:00