Lex Rivera
Lex Rivera
Well we can just rename it to "security hardening of tempo-distributed", maybe. Initial adding of /var/tempo emptyDir was done to make it compatible with security best practices, so, IMO, makes...
Sure, why not. Should it be configurable, or static will be enough?
Interesting, now it fails after bump to 1.5.0. Ingester fails to assemble ring?
@joe-elliott in distributor: ``` level=error ts=2022-08-17T18:57:58.684074925Z caller=main.go:109 msg="error running Tempo" err="failed to init module services error initialising module: usage-report: failed to initialize usage report: mkdir /var/tempo: read-only file system" ```...
I can add emptyDir back for distributor. Kludge for sure, but will work. Another way will be to test it against something like minio, but that's completely different story.
It looks like github is acting finicky now, throwing random 503s and failing pipelines
Yep, looks like that did the trick.
i added support for structuredConfig (like in loki and mimir) to tempo-distributed: https://github.com/grafana/helm-charts/pull/1591 As soon as it will be merged it should be easy to customize any variable you want
any updates on this one? Got same issue with scaleway.
>Could you give a bit more context about the labels? Is that just adding the common Kubernetes labels to the generated PrometheusRule CRs? Yes, precisely