grafana/tempo-operator

Local Backend type

Closed this issue · 2 comments

gunpuz commented

How to deploy tempo without s3, gcs, azure using only "plain" kubernetes?

Tempo docs says there is fourth option - local
https://github.com/grafana/tempo/blob/56fbbcd107f7853e3e8f64df1e22f37a24cd367f/docs/sources/tempo/operations/tempo_cli.md?plain=1#L43

`--backend <value>` The storage backend type, one of `s3`, `gcs`, `azure`, and `local`.

Here seems to be only 3 options:

switch tempo.Spec.Storage.Secret.Type {

hi @gunpuz!

Tempo supports local filesystem mode only in the monolithic deployment mode, because all components need to access the same disk: https://grafana.com/docs/tempo/latest/configuration/#storage

At the moment the Tempo operator only supports the microservices deployment mode. However, I'm currently working on supporting the monolithic mode, which will support local filesystem storage (in a PersistentVolume) and also in-memory storage: #710.

I'm closing this in favor of #710, which is already worked on here: #722.