Skip to content

Conversation

@maynardflies
Copy link
Contributor

Summary

  • Adds extraVolumes and extraVolumeMounts fields to the jaeger deployment values, restoring the ability to mount custom volumes (PVCs, secrets, configmaps, etc.) on the Jaeger pod
  • The v4.2.0 chart rewrite simplified the deployment to only support ConfigMap volumes for user-config and ui-config, which broke storage backends like Badger that require persistent volumes
  • Follows the same pattern already used by spark, esIndexCleaner, esRollover, and esLookback job templates

Fixes #737

Test plan

  • helm lint charts/jaeger passes
  • helm template renders correctly with default values (no extra volumes)
  • helm template renders correctly with extra volumes/mounts set (PVC and mountPath appear in output)
  • CI values files render cleanly

The v4.2.0 chart rewrite removed the ability to mount custom volumes
on the Jaeger deployment, which is needed for storage backends like
Badger that require local persistent volumes.

This adds extraVolumes and extraVolumeMounts fields to the jaeger
values section, following the same pattern already used by the spark,
esIndexCleaner, esRollover, and esLookback job templates.

Fixes jaegertracing#737

Signed-off-by: Greg Olmstead <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Add extraVolumes/extraVolumeMounts support to jaeger deployment

1 participant