feat: Add support for custom volumes and volume mounts in HA chart#201
Merged
feat: Add support for custom volumes and volume mounts in HA chart#201
Conversation
antejavor
approved these changes
Feb 20, 2026
11 tasks
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
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.
What
This PR adds support for custom volumes and volume mounts in the
memgraph-high-availabilitychart for both data instances and coordinators. New valuesstorage.data.extraVolumes,storage.data.extraVolumeMounts,storage.coordinators.extraVolumes, andstorage.coordinators.extraVolumeMountsare introduced invalues.yaml.The
templates/data.yamlandtemplates/coordinators.yamlStatefulSet templates are updated to conditionally render extra volumes and include a hardcodedbolt-certsSSLvolume mount.
Why
Users need a way to mount arbitrary volumes (e.g. TLS certificates from Kubernetes Secrets) into Memgraph pods. The primary use case is mounting Bolt SSL certificates for
encrypted client connections, but the
extraVolumes/extraVolumeMountspattern is generic enough to support other scenarios (config files, additional storage, etc.).How
values.yaml: AddedextraVolumes: []andextraVolumeMounts: []under bothstorage.dataandstorage.coordinators, with commented examples showing how to mount a TLSSecret as a volume.
templates/data.yaml: Added a conditionalvolumes:block that rendersstorage.data.extraVolumeswhen non-empty. Added a hardcodedbolt-certsvolume mount at/etc/memgraph/ssl(readOnly).templates/coordinators.yaml: Same changes asdata.yamlbut scoped to coordinator StatefulSets, usingstorage.coordinators.extraVolumes.