linkerd
/
linkerd2
mirror of https://github.com/linkerd/linkerd2.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
linkerd2/charts/add-ons/grafana
History
Alex Leong cdc57d1af0
Use linkerd-jaeger extension for control plane tracing (#5299) 
Now that tracing has been split out of the main control plane and into the linkerd-jaeger extension, we remove references to tracing from the main control plane including:

* removing the tracing components from the main control plane chart
* removing the tracing injection logic from the main proxy injector and inject CLI (these will be added back into the new injector in the linkerd-jaeger extension)
* removing tracing related checks (these will be added back into `linkerd jaeger check`)
* removing related tests

We also update the `--control-plane-tracing` flag to configure the control plane components to send traces to the linkerd-jaeger extension.  To make sure this works even when the linkerd-jaeger extension is installed in a non-default namespace, we also add a `--control-plane-tracing-namespace` flag which can be used to change the namespace that the control plane components send traces to.

Note that for now, only the control plane components send traces; the proxies in the control plane do not.  This is because the linkerd-jaeger injector is not yet available.  However, this change adds the appropriate namespace annotations to the control plane namespace to configure the proxies to send traces to the linkerd-jaeger extension once the linkerd-jaeger injector is available.

I tested this by doing the following:

1. bin/linkerd install | kubectl apply -f -
1. bin/helm install jaeger jaeger/charts/jaeger
1. bin/linkerd upgrade --control-plane-tracing=true | kubectl apply -f -
1. kubectl -n linkerd-jaeger port-forward svc/jaeger 16686
1. open http://localhost:16686
1. see traces from the linkerd control plane

Signed-off-by: Alex Leong <alex@buoyant.io>
 		2020-12-08 14:34:26 -08:00
..
templates Use linkerd-jaeger extension for control plane tracing (#5299) 2020-12-08 14:34:26 -08:00
.helmignore Move grafana templates into a separate sub-chart as a add-on (#4320) 2020-05-11 22:22:14 +05:30
Chart.yaml Move grafana templates into a separate sub-chart as a add-on (#4320) 2020-05-11 22:22:14 +05:30
README.md Add automatic readme generation for charts (#5316) 2020-12-02 14:37:45 -05:00
README.md.gotmpl Add automatic readme generation for charts (#5316) 2020-12-02 14:37:45 -05:00
requirements.lock Move grafana templates into a separate sub-chart as a add-on (#4320) 2020-05-11 22:22:14 +05:30
requirements.yaml Move grafana templates into a separate sub-chart as a add-on (#4320) 2020-05-11 22:22:14 +05:30
values.yaml Add automatic readme generation for charts (#5316) 2020-12-02 14:37:45 -05:00

README.md

grafana

A Helm chart for the grafana add-on in Linkerd

Version: 0.1.0

AppVersion: 1.0

Requirements

Repository Name Version
file://../../partials partials 0.1.0

Values

Key Type Default Description
image.name string "ghcr.io/linkerd/grafana" Docker image name for the grafana instance
image.tag string nil Docker image tag for the grafana instance
proxy.resources string nil Structure analog to the resources fields above, but overriding the resources of the linkerd proxy injected into the grafana pod.
resources.cpu.limit string nil Maximum amount of CPU units that the grafana container can use
resources.cpu.request string nil Amount of CPU units that the grafana container requests
resources.memory.limit string nil Maximum amount of memory that grafana container can use
resources.memory.request string nil Amount of memory that the grafana container requests

Autogenerated from chart metadata using helm-docs v1.4.0