Maarten De Wispelaere

> In tempo-query-frontend pod, in tempo-query container, following error is present: > > ``` > 2022-08-07T14:09:06.263Z [ERROR] tempo-query: plugin init error: error="open /tmp/plugin164587256: read-only file system" timestamp=2022-08-07T14:09:06.263Z > ``` Wouldn't...

> Should we also set default securitycontext, like it's done in mimir and loki charts? I run mine with > > ``` > - tempo: > securityContext: > capabilities: >...

While at it, we might as well also add: ``` automountServiceAccountToken: false enableServiceLinks: false ``` But as @joe-elliott mentioned earlier, it's a lot of changes that have nothing to do...

Was just discussing it with Elliot ; he said the same thing :D How about my 2 suggestions ?

> Sure, why not. Should it be configurable, or static will be enough? personally I would go for static - I don't see the added value of making it configurable.

Merging time! Thanks for your contribution @rlex 🚀

@BenCoughlan15 Please be so kind to sign the DCO and CLA so we can merge your contribution?

Hey @BenCoughlan15 ; the DCO one is still failing: https://github.com/grafana/helm-charts/pull/1669/checks?check_run_id=7893931132 Next to that, you'll also need a chart version bump: 0.16.1 for example

@nielstenboom seems like something went wrong with the docs? The docs for `multitenancy_enabled` have disappeared?

@nielstenboom holidays happened ;) - would you be able to resolve the conflicts ?