tempo-query no longer supports grpc-plugin

Summary

Tempo-Query v2.6.0 introduced a breaking change in the way it deploys Jaeger:

• BREAKING CHANGE tempo-query is no longer a Jaeger instance with grpcPlugin. It’s now a standalone server. Serving a gRPC API for Jaeger on 0.0.0.0:7777 by default. [PR 3840]

from: https://grafana.com/docs/tempo/next/release-notes/v2-6/#other-breaking-changes

Steps to reproduce

Deploying as part of a Tempo Renovate for Big Bang: big-bang/product/packages/tempo!144 (merged)

What is the current bug behavior?

Attempting to update Tempo/Tempo-Query from 2.5.0 to 2.6.1 container results in a CrashLoopBackoff state with this error:

2024/12/09 14:37:23 Cannot initialize storage factory: unknown storage type grpc-plugin. Valid types are [cassandra opensearch elasticsearch memory kafka badger blackhole grpc]

What is the expected correct behavior?

Tempo-Query container deploys successfully

Relevant logs and/or screenshots

See above

Possible fixes

May need to realign to upstream? See most recent commit on: https://github.com/grafana/tempo/blob/v2.6.1/cmd/tempo-query/Dockerfile

Tasks

• Bug has been identified and corrected within the container

Please read the Iron Bank Documentation for more info