Deprecated configuration warning in the log after the upgrade of the operator

[sankosa]

We use tempo operator to deploy our tempo intances.
We have upgraded our tempo operator from v0.14.0 to v0.15.3.
After the upgrade, the operator also upgraded our tempo instance from 2.6.1 to 2.7.1.
The upgrade is successful and the new version of tempo is up and running. Despite this, we see the following warnings in the logs:
"msg="c.StorageConfig.Trace.Cache is deprecated and will be removed in a future release." explain="Please migrate to the top level cache settings config."

We can not solve this issue/warning, because the default config is provided by the operator and saved in a configmap. The configmap contains two config files:

• tempo-query-frontend.yaml:
• tempo.yaml
  Both config file has the storage.trace.cache setting what we can not change.

To Reproduce
Deploy tempo with tempo operator 2.7.1.
You will see the warning in the logs of every tempo component/pod.

Expected behavior
Operator creates a default config which is error/warning free.

Environment:

• Infrastructure: Kubernetes
• Deployment tool: kustomize (tempo operator)

Additional Context

[joe-elliott]

This seems like a tempo operator issue which is maintained by RedHat and primarily @andreasgerstmayr. I'll move it over there.