ldap.toml currently not created about grafana-operator HOT 7 CLOSED

Creating ldap.toml is currently not directly supported. However, the Grafana CR allows you to specify a list of secrets that are added to the Grafana pod as volumes (see the docs here). The name of the extra volume will be secret-<secret name>. You could have a Secret with a key ldap.toml and the file contents as the value and use this mechanism to mount it to a directory inside the Grafana pod.

An example of how we use this can be found here: https://github.com/integr8ly/application-monitoring-operator/blob/master/templates/grafana.yaml#L48

I agree that ConfigMaps would be more suitable but currently the Grafana CR only accepts a list of secrets. But i'm thinking about adding configmap mounting support for a while.

Please let me know if this works for you.

from grafana-operator.

Sorry, we don't currently create volume mounts for those extra volumes in the Grafana pod. So this won't work. But thats a good use case for it and we should probably implement it.

from grafana-operator.

I wonder why not implement handling of GrafanaConfigAuthLdap instead?

from grafana-operator.

I'd like to keep it as generic as possible. Being able to mount files into the Grafana pod in combination with the the configuration in the Grafana CR should work for your use case and probably a number of others as well.

from grafana-operator.

I'd like to keep it as generic as possible.

So rather remove GrafanaConfigAuthLdap and insert an init-container, which then copies content of configMaps into volumes!?

from grafana-operator.

No, the idea is not to remove GrafanaConfigAuthLdap. I'm not familiar with LDAP configuration in Grafana, but it looks like the following is needed:

1. Configure LDAP as described in the Grafana docs. This is already possible with GrafanaConfigAuthLdap. You need to provide a path to ldap.toml in that config, so...
2. ...give users a way to provide ldap.toml in the Grafana pod. Using a ConfigMap is probably the way to go and the idea is to allow mounting configmaps as volumes (and volumemounts) via the Grafana CR.

It would probably look something like this:

apiVersion: integreatly.org/v1alpha1
kind: Grafana
...
spec:
  config:
    auth.ldap:
      config_file: "/etc/configmaps/ldap-toml/ldap.toml"
  configmaps:
    - ldap-tomp
...

The operator would then automatically add a volumes for all configmaps to the Grafana pod and also mount every configmap under /etc/configmaps/<config map name>. Keys in the configmap would be available as files in this directory.

This is also how its implemented in the Prometheus operator. Do you think that would cover all requirements for configuring LDAP?

from grafana-operator.

ping @abergmeier. The proposed solution is now implemented in #49 , mind giving it a try?

from grafana-operator.