Describe the bug a clear and concise description of what the bug is.

Hello,
As described in former repo issue the issue is still present in 2.6.2 chart for tempo-distributed.

Using:

extraArgs:
    - -config.expand-env=true
  extraEnvFrom:
    - secretRef:
        name: some-secret

Results in templates being rendered in memcached and at least the extraArgs section triggers a CrashLoopBackoff:

Maximum connections must be greater than 0

What's your helm version?

3.18.0

What's your kubectl version?

1.34.4

Which chart?

tempo-distributed

What's the chart version?

2.6.2

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

No response

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

helm install tempo

Anything else we need to know?

No response