do not store secrets in configmaps

[vixns]

No description provided.

[th0th]

Thanks for the PR 💐

Even tough I agree with the idea of "not storing sensitive information in the configmap", it doesn't feel right to move all configuration to a secret. If there is a way to separate configuration options like hosts, ports etc from sensitive information, we can go that way maybe?

[vixns]

"One or more TOML files can be read by passing --config config.toml multiple times. " ( source: https://listmonk.app/docs/configuration/ )
Splitting the configuration between a CM and a secret seems doable, it depends how toml files are merged. Another way would be to use environment variables for non sensitive content instead of a configmap.

[th0th]

"One or more TOML files can be read by passing --config config.toml multiple times. " ( source: https://listmonk.app/docs/configuration/ ) Splitting the configuration between a CM and a secret seems doable, it depends how toml files are merged. Another way would be to use environment variables for non sensitive content instead of a configmap.

Do you know if there is any configuration that is doable by the config file, but not the environment variables? If everything is configurable by environment variables, we can go that way, and move sensitive information to a secret.

[elthariel]

Secrets aren't that secret in k8s, but in doubt, it's better to have everything in a secret than having a secret in a configmap :)