linkerd2/doc
Andrew Seigner 291d8e97ab
Move injected data from env var to k8s labels (#605)
The inject code detects the object it is being injected into, and writes
self-identifying information into the CONDUIT_PROMETHEUS_LABELS
environment variable, so that conduit-proxy may read this information
and report it to Prometheus at collection time.

This change puts the self-identifying information directly into
Kubernetes labels, which Prometheus already collects, removing the need
for conduit-proxy to be aware of this information. The resulting label
in Prometheus is recorded in the form `k8s_deployment`.

Signed-off-by: Andrew Seigner <siggy@buoyant.io>
2018-03-23 16:11:34 -07:00
..
images Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
README.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
adding-your-service.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
debugging-an-app.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
get-involved.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
getting-started.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
overview.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00
prometheus.md Move injected data from env var to k8s labels (#605) 2018-03-23 16:11:34 -07:00
proxy-metrics.md Move injected data from env var to k8s labels (#605) 2018-03-23 16:11:34 -07:00
roadmap.md Move Conduit documentation sources to Conduit repo. (#418) 2018-02-28 13:39:28 -10:00

README.md

The documentation here is published at https://conduit.io/docs/ when each version is released. The version of the documentation in GitHub should always match the code in the same branch. For example, when a pull request changes the behavior of a documented feature, the pull request should change the documentation here to match the new behavior.