feat: expose hyperdx initContainers, volumes, volumeMounts passthrough#218
Merged
Conversation
… passthrough
Adds three optional fields under hyperdx.deployment:
- initContainers: appended after wait-for-mongodb when mongodb.enabled,
or used alone when mongodb is disabled
- volumes: rendered at pod spec level
- volumeMounts: rendered on the app container
Defaults are empty lists, so existing values files render byte-identical YAML with no behavior change. Enables common Kubernetes patterns such as fetching certificates at startup, mounting external secrets, or attaching ConfigMap files without forking the chart.
Includes unit tests covering defaults, user-provided values, ordering when both mongodb and user init containers are set, and full passthrough of fields like subPath and readOnly.
🦋 Changeset detectedLatest commit: 231b640 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds three optional passthrough fields under
hyperdx.deploymentso users can inject standard Kubernetes pod-spec extension into the HyperDX Deploymenthyperdx.deployment.initContainers: appended afterwait-for-mongodbwhenmongodb.enabledis true; rendered standalone when MongoDB is disabledhyperdx.deployment.volumes: rendered atspec.template.spec.volumeshyperdx.deployment.volumeMounts: rendered on theappcontainerUnit tests included
Motivation
Several common deployment patterns currently require forking this chart, for eg:
/etc/hyperdx/idp-cert.pemExposing these standard hooks keeps these workflows in user values files instead of chart forks.
Backward compatibility
Backward compatible. Defaults are empty lists. The existing
should include initContainers when mongodb.enabled is truetest continues to pass unchanged, confirming no behavior change for current users.Changeset included.