Add tls_insecure_skip_verify to Tempostack CRD when using tempo operator

[mikhatanu]

Grafana Tempo has a config tls_insecure_skip_verify in storage config, but tempostack crd has no option to include it (changing configmap does not work because it is managed by operator). The option is good for self-hosted object storage like minio that use self-signed certificate.

[andreasgerstmayr]

Grafana Tempo has a config tls_insecure_skip_verify in storage config, but tempostack crd has no option to include it (changing configmap does not work because it is managed by operator).

There are two workarounds possible at the moment:

• set the CRD to Unmanged (see

  tempo-operator/docs/spec/tempo.grafana.com_tempostacks.yaml

  Line 40 in f4cb97c

  managementState: "Managed" # ManagementState defines if the CR should be managed by the operator or not. Default is managed.

  ). This means the operator stops reconciling (updating) its managed objects until you change it back to Managed state
• use the extraConfig setting: with this setting you can make arbitrary modifications to the Tempo config. The operator merges the generated configuration with the user-supplied configuration (from extraConfig). Example: https://developers.redhat.com/articles/2024/08/14/introducing-tempo-monolithic-mode#configuring_retention