Add support for Datasource Custom query parameters (customQueryParame…

[kirchknopfc]

Description

Grafana has an option to define Custom query parameters on an Prometheus data source.
Basically, it means that this query parameter add to the Promtheus or Thanos queries.

The query parameter example is required if OpenShift's user-defined monitoring is used as Prometheus datasource.
The OpenShift thanos-querier (https://thanos-querier.openshift-monitoring.svc.cluster.local:9092) needed the URL parameter "namespace=yournamespace" in the query as parameter.

The option on the Prometheus datasource is called "Custom query parameters" (customQueryParameters) in the section "Misc":

The proposed change adds support for set the Custom query parameters via the GrafanaDatasource CRD.

Relevant issues/tickets

PR #309

Type of change

• New feature (non-breaking change which adds functionality)

Checklist

• This change requires a documentation update
  I've added an example below, you might want to include it in the documentation. But not all option are documented

• I have added a test case that will be used to verify my changes

• Verified independently on a cluster by reviewer

Verification steps

1. Deploy a data source (GrafanaDatasource) with the following specification:

apiVersion: integreatly.org/v1alpha1
kind: GrafanaDataSource
metadata:
  name: test-grafanadatasource
spec:
  name: prometheus.yaml
  datasources:
    - name: Prometheus
      type: prometheus
      access: proxy
      url: https://thanos-querier.openshift-monitoring.svc.cluster.local:9092
      isDefault: true
      version: 1
      editable: true
      jsonData:
        tlsSkipVerify: true
        customQueryParameters: "namespace=ns1"

2. In Grafana go to the data source settings (Configuration -> Datasources -> Prometheus)
   The Custom query parameters option should be set to "namespace=ns1".
   

[openshift-ci-robot]

Hi @kirchknopfc. Thanks for your PR.

I'm waiting for a integr8ly member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kirchknopfc]

/assign @pb82

[HVBE]

see inline comment, once that's addressed I'm happy to merge this in 👍

[HVBE]

/lgtm, thanks for contributing @kirchknopfc

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HubertStefanski

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [HubertStefanski]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[HVBE]

/lgtm