Optionally pass cortex config as configmap.

[jmcarp]

What this PR does:
Optionally pass cortex config as configmap.

Note: I only updated the ingestor templates so far, to verify that the approach makes sense. If it does, I'll copy and paste the updated volume to the other templates.

Which issue(s) this PR fixes:
Fixes #235.

Checklist

• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[nschad]

Nice!

with that approach however, we should really have the s3 credentials (or similiar) not in the configMap. I'm not saying Secrets are "secure" but atleast you can install some KMS provider where you can actually encrypt the data.

But with extraVolumes, extraVolumeMounts, extraEnvs and extraArgs this should already be possible. I would have to test that but I think you can already have sensitive information separately. Use environment variables in the configuration

[nschad]

Hey, thank you for your contribution.

Can you please add the CHANGELOG.md entry?
Also we would need to add a mechanism similiar to: This
We should also have ci-tests setup and documentation guide for proper usage so nobody puts their secrets in the configmap

So we can restart components when configmap changes, right now we can't use something like configmap reloader AFAIK

[jmcarp]

Updated, lmk if I missed anything.

[nschad]

I will have another glance tomorrow but this looks really good. Thanks!

[nschad]

I re-edited the guide, because inline code blocks completely broke the the text unfortunately. We will have to adjust the markdown processor or something like that in the future

[nschad]

@jmcarp Please be careful when rebasing, my changes to the guide were lost 😢

[jmcarp]

Ack, sorry, not used to collaborating on a branch 😓