<p>I have one question about Grafana. How I can use exiting Prometheus deamonset on GKE for Grafana. I do not want to spin up one more Prometheus deployment for just Grafana. I come up with this question after I spin up the GKE cluster. I have checked <code>kube-system</code> namespace and it turns out there is Prometheus <code>deamonset</code> already deployed. </p>

<pre><code>$ kubectl get daemonsets -n kube-system
NAME                       DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR                                  AGE
prometheus-to-sd           2         2         2       2            2           beta.kubernetes.io/os=linux                    19d
</code></pre>

<p>and I would like to use this Prometheus</p>

<p>I have Grafana deployment with helm <code>stable/grafana</code></p>

<pre><code>$ kubectl get deploy -n dev
NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
grafana                   1/1     1            1           9m20s
</code></pre>

<p>Currently, I am using <code>stable/prometheus</code></p>

Farkhod Sadykov
<p>prometheus-to-sd is not a Prometheus instance, but a component that allows getting data from Prometheus to GCP's stackdriver. More info here: <a href="https://github.com/GoogleCloudPlatform/k8s-stackdriver/tree/master/prometheus-to-sd" rel="nofollow noreferrer">https://github.com/GoogleCloudPlatform/k8s-stackdriver/tree/master/prometheus-to-sd</a></p>

<p>If you'd like to have Prometheus you'll have to run it separately. (<a href="https://github.com/helm/charts/tree/master/stable/prometheus-operator" rel="nofollow noreferrer">prometheus-operator helm chart</a> is able to deploy whole monitoring stack to your GKE cluster easily (which my or may not be exactly what you need here).</p>

<p>Note that recent Grafana versions come with Stackdriver datasource, which allows you to query Stackdriver directly from Grafana (if all metrics you need are or can be in Stackdriver).</p>
