What happened?
As a user deploying Jaeger v2 with a storage backend that requires local volumes (e.g. Badger), I want to be able to specify extra volumes and
volume mounts on the jaeger deployment, so that I can mount PVCs, secrets, or other volumes without needing to fork the chart.
The v4.2.0 rewrite simplified the chart to a stateless model targeting external storage (Elasticsearch, Cassandra) or in-memory for testing.
However, Jaeger v2 still supports Badger as a storage backend via userconfig, and users can configure it to write to local directories — but
there's no way to mount a volume at those paths since the deployment template only supports ConfigMap volumes for user-config and ui-config.
extraObjects can't work around this either — it can create additional resources (PVCs, ConfigMaps, etc.) but can't inject volumes or
volumeMounts into the chart's own Deployment template. The only workaround is setting jaeger.enabled: false and recreating the entire
Deployment via extraObjects, which defeats the purpose of using the chart.
Adding extraVolumes and extraVolumeMounts fields to the jaeger values section is a common Helm chart pattern (already used in this chart's
spark, esIndexCleaner, esRollover, and esLookback jobs via extraSecretMounts/extraConfigmapMounts) and would cover this use case without
re-adding dedicated Badger support.
Steps to reproduce
- Try and use badger with persistent storage
Expected behavior
Have the ability to attach additional volumes as we could in 4.1.x
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
What happened?
As a user deploying Jaeger v2 with a storage backend that requires local volumes (e.g. Badger), I want to be able to specify extra volumes and
volume mounts on the jaeger deployment, so that I can mount PVCs, secrets, or other volumes without needing to fork the chart.
The v4.2.0 rewrite simplified the chart to a stateless model targeting external storage (Elasticsearch, Cassandra) or in-memory for testing.
However, Jaeger v2 still supports Badger as a storage backend via userconfig, and users can configure it to write to local directories — but
there's no way to mount a volume at those paths since the deployment template only supports ConfigMap volumes for user-config and ui-config.
extraObjects can't work around this either — it can create additional resources (PVCs, ConfigMaps, etc.) but can't inject volumes or
volumeMounts into the chart's own Deployment template. The only workaround is setting jaeger.enabled: false and recreating the entire
Deployment via extraObjects, which defeats the purpose of using the chart.
Adding extraVolumes and extraVolumeMounts fields to the jaeger values section is a common Helm chart pattern (already used in this chart's
spark, esIndexCleaner, esRollover, and esLookback jobs via extraSecretMounts/extraConfigmapMounts) and would cover this use case without
re-adding dedicated Badger support.
Steps to reproduce
Expected behavior
Have the ability to attach additional volumes as we could in 4.1.x
Relevant log output
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs