Skip to content

Latest commit

 

History

History
54 lines (41 loc) · 1.64 KB

plugins.md

File metadata and controls

54 lines (41 loc) · 1.64 KB
Raw

Plugins

Install plugins as dependencies of datasources or dashboards

If a datasource or dashboard requires a plugin, it can be defined within a dashboard that it is used in, this will install the plugin, the datasource can be parsed regardless of the fact if the plugin exist (yet). Once defined in a dashboard, the operator should install the plugin and make it accessible to the datasource. If a plugin already exists then the operator will not attempt another installation.

Install plugins using Grafana env vars via the operator

The operator allows you to pass custom env vars to the grafana deployment. This means that you can set the GF_INSTALL_PLUGINS flag, as described in install-official-and-community-grafana-plugins

These can be added to the spec.deployment.envFrom section of the Grafana CR. EG:

spec:
  ...
  deployment:
    envFrom:
      - secretRef:
          name: grafana-env

apiVersion: v1
kind: Secret
metadata:
  name: grafana-env
  namespace: default
stringData:
  GF_INSTALL_PLUGINS: doitintl-bigquery-datasource 1.0.8

If the plugin doesn't install, try restarting the grafana deployment.

Install plugins through a HTTP(S) Proxy

To install plugins through a HTTP(S) Proxy, you will have to define the spec.deployment.HttpProxy section of the Grafana CR. EG:

If you need to use HTTPS, please add your HTTPS proxy URL to the secureURL section.

spec:
  ...
  deployment:
    HttpProxy:
      enabled: true
      url: <your proxy URL here>
      secureURL: <your HTTPS proxy URL here>