OperatorHub.io contribution

[david-martin]

Follow through contribution steps on https://operatorhub.io/contribute to add the Grafana Operator to OperatorHub.io

cc @pb82 for checklist of changes before you're happy to have a v1 on OperatorHub

• Grafana plugin support via GrafanaDashboard CR Plugins #6
• Use an upstream Grafana image, with ability to change/specify a different image Configurable image #8
• Allow custom containers e.g. for oauth proxy allow extra containers in cr #9
• Allow a namespace selector to specify where to look for CRs Watch namespaces based on CR value #4 rename namespace selector #5
• Auto update dashboards configmap when GrafanaDashboard CR's change
• Update to latest operator-sdk version
• Test & Verify the Operator manually https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md#manual-testing-on-kubernetes
• Preview the Operator as per https://github.com/operator-framework/community-operators#preview-your-operator-on-operatorhubio
• Submit Pull request to https://github.com/operator-framework/community-operators (Kubernetes and OpenShift compatible)

[wei-lee]

@pb82 nice work. we are trying to do the same but we are having trouble with Ingress. Are you using ingress as well? if so are you able to get it work with oauth-proxy?

[david-martin]

@wei-lee for OpenShift, something outside the operator would create the route. Same for Kubernetes and Ingress
If using something like oauth proxy, the container for that would be defined in the Grafana CR and included in the Grafana Pod.
So the default install doesn't include any Route, Ingress or OAuth Proxy. This allows it to work on Kubernetes out of the box.

See the application-monitoring-operator for an example of how you could create a Route & setup OAuth Proxy with Prometheus.

• Route creation: https://github.com/integr8ly/application-monitoring-operator/blob/master/pkg/controller/applicationmonitoring/applicationmonitoring_controller.go#L160-L165
• OAuth Proxy & ServiceAccount changes integr8ly/application-monitoring-operator@ebfdbff.

This is the pattern the Grafana Operator will follow, so expect changes to the application-monitoring-operator soon for that.

[seravat]

Hey guys, any idea when the operator will be available on operatorhub? We have an interested client, which is currently using it without any lifecycle management.

[pb82]

@seravat We're in the process of preparing and submitting the operator, see #30 . Once this is merged i'm going to open the PR to add the operator to operatorhub.io.

A few caveats though when installing from operatorhub:

1. by default, the operator will only discover dashboards in it's own namespace. To discover dashboards in other namespaces you have to manually apply the cluster roles (deploy/cluster_roles) and add the --scan-all flag to the container in the deployment.
2. the operator will not create a route to Grafana by default, but you can easily force it to create the route by adding createRoute: True to the Grafana CR spec.

We're going to look into better multi-namespace support in upcoming releases of the operator.

[seravat]

Thank you Peter! Looks good

[pb82]

It's listed now: https://operatorhub.io/operator/grafana-operator
It should also be available in the OpenShift 4 catalog