Idea: API for read/write of runtime configuration

[pjastrzabek]

What is the problem you are trying to solve?

We deploy various applications in our testing pipelines and for each release we configure it with a sidecar that sends logs / metrics to separate tenant (let's say "app_version_xx").

We use shared mimir stack that is used for other purposes so default retention is set to 30 days, but for these adhoc tenants we want to set it to something shorter like 1day.
Each time we run pipeline, currently we need to log into kubernetes cluster, edit config map with runtime settings, add proper setting with an extra care for indentation (a mistake in this file, can render file to no longer reloading itself with a warning message in logs (which is good)).

We automated this, but we miss general API for reading / changing runtime settings. API that would work on json.

Which solution do you envision (roughly)?

• having an API that returns json for reading runtime settings for all tenants / single tenant
• having an API for setting runtime setting for tenant

Have you considered any alternatives?

We work on configmap with runtime settings directly, but it's error prone.

Any additional context to share?

No response

How long do you think this would take to be developed?

Small (<= 1 month dev)

What are the documentation dependencies?

No response

Proposer?

No response

[colega]

Hi,

We are not planning to add such features to Grafana Mimir. Adding an API to Grafana that would just edit the configmap sounds weird.

Each time we run pipeline, currently we need to log into kubernetes cluster, edit config map with runtime settings.
...
We automated this.

Can you explain which part you automated and how so I can provide you some guidance/hints on how to achieve what you need with least effort?
In general terms, seems like you want some gitops that validates that config is valid (by running mimir as CI step) and then just render that.

add proper setting with an extra care for indentation
...
API that would work on json.

Note that you can already render overrides as JSON, since JSON is valid YAML.