Add support for storing configuration in configmap

[anilarora]

Today, the operator stores the configuration of the telegraf sidecar in a secret. Our environments are restricted on who can create secrets, so it is preferable to use a configmap instead. And as our configuration never has a credential stored in it, this would be safe for us to use. Would like a feature enhancement to enable storing configuration in a configmap instead.

Relevant URLs

Would work well with #122

What products and version are you using?

Telegraf Operator 1.3.8

[eli-cook]

This is interesting to me, I am actually working on a fork that allows you to define a configmap location in an annotation telegraf.influxdata.com/env-configmap: <configmap-name>

As a single annotation, and the configmap would have values corresponding to the currently supported set of configuration annotations today. Something like this

configmap := &corev1.ConfigMap{ ObjectMeta: metav1.ObjectMeta{ Name: "my-config", Namespace: "mynamespace", }, Data: map[string]string{ "telegraf.influxdata.com/port": "6060", "telegraf.influxdata.com/path": "/metrics", }, }
Is this what you were describing?