Add custom volumeclaimtemplates #163
Merged
Conversation
This file contains 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
added 2 commits
August 7, 2024 16:29
Signed-off-by: Sebastian Lang <sebastian.lang@damovo.com>
Signed-off-by: Sebastian Lang <sebastian.lang@damovo.com>
SebastianLng
changed the title
KongZ
approved these changes
Aug 9, 2024
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 does / why we need it
This adds the option to specify additional volume claim templates. This is helpful if you require additional storage which is not a common volume but separate for each Graylog pod. It also helps with deployments which need extra files and only use local storage so using a common PVC for all pods is not possible.
Which issue this PR fixes
Not an open issue in GitHub, but something we'd like to use for our deployments.
Special notes for your reviewer
Checklist