Add support for additional volumes and volume mounts (with fixes) #62
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
This PR adds support for configuring additional volumes and volume mounts on the IQ Server main container, based on the work in PR #51 by @sleyer.
This implementation includes several improvements and fixes to ensure the feature produces clean, idiomatic Kubernetes YAML and has accurate documentation.
Changes
Feature Implementation (from PR #51)
extraVolumesconfiguration supporting:existingClaim)extraVolumeMountsconfiguration with:name,mountPathsubPath,readOnlyImprovements & Fixes
Fixed volumeMounts rendering (Critical)
subPath: ""andreadOnly:hasKeycheck forreadOnlyto handle explicitfalsevaluesFixed documentation errors
subpath→subPath(capital P)Updated test expectations
Improved test metadata
Testing
All changes verified with:
helm lint chart/- passes with no errorsExample Rendering
Before (with fixes):
Previously:
Use Case
This feature enables users to mount custom certificates, configuration files, or other resources into the IQ Server container via ConfigMaps, Secrets, or other Kubernetes volume types.
Related
Checklist