Skip to content

Conversation

sina-grz
Copy link

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:

  • Pass an isArbiter boolean to the build function
  • Apply arbiter-optimized defaults when isArbiter=true:
    • No PVC
    • Minimal resources
  • Maintain current behavior for data members
  • Keep spec.statefulSet for member customization only

All Submissions:

  • ✅ Have you opened an Issue before filing this PR?
  • ✅ Have you signed our CLA?
  • ✅ Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • [?] Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant