feat: PVC configurable through values.yml #1083
Open
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.
This pull request includes changes to the Helm chart templates and configuration files to allow customization of Persistent Volume Claim (PVC) names and volume names for both data and audit storage. The most important changes include updates to the templates, schema, and values files to support these new configuration options.
Enhancements to PVC customization:
templates/_helpers.tpl
: Updated to allow specifying custom names for data and audit PVCs and added support for specifying volume names. [1] [2] [3]values.schema.json
: Added new propertiesname
andvolumeName
for bothdataStorage
andauditStorage
objects to support the new customization options. [1] [2]values.yaml
: Introduced new fieldsname
andvolumeName
underdataStorage
andauditStorage
configurations to allow users to set custom PVC names and volume names. [1] [2] [3] [4]