Make sizing presets resource-oriented#197
Merged
Merged
Conversation
bruno-espino
force-pushed
the
bruno/resource-oriented-query-presets
branch
from
July 22, 2026 17:15
c284ec4 to
bc9f278
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Make sizing presets resource-oriented by deriving FusionFire query cost capacity from effective CPU, normalizing stable application pod shapes, and using the tiny preset as the canonical internal fallback.
Upgrade notes
No-preset FusionFire workloads now use the tiny preset baseline and may increase its resources compared with earlier chart versions. Operators running constrained clusters should select a sizing preset or configure explicit workload resources.
Breaking changes
None.