separate statefulset templating for arbiters and members #1738
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:
I previously described the problems and possible solutions in this issue:
#1737
This branch implements the second proposed solution: Context-Aware Default Templates.
The goal is to avoid unnecessary resource waste by providing separate defaults for arbiters vs. data members while keeping customization consistent.
Implementation:
isArbiter
boolean to the build functionisArbiter=true
:spec.statefulSet
for member customization onlyAll Submissions:
closes #XXXX
in your comment to auto-close the issue that your PR fixes (if such).