feat(canopy): size upgrade replicas for large deployments - #146
Closed
dannash100 wants to merge 1 commit into
Closed
dannash100 wants to merge 1 commit into
dannash100 wants to merge 1 commit into
Conversation
dannash100
marked this pull request as draft
September 16, 2026 22:39
dannash100
force-pushed
the
upgrade-intent-sizing
branch
from
September 16, 2026 22:43
abbcee3 to
887e5af
Compare
dannash100
force-pushed
the
upgrade-intent-sizing
branch
from
September 16, 2026 23:32
887e5af to
c4aa03a
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.
Not sure we need this - kinda on standby for Samoa test incoming
An upgrade replica writes a whole migration batch into a volume sized 1.1x its snapshot. At 12 GB that left slack; at 119 GB a table rewrite or index build can fill it, and a full volume reports a failed migration for a deployment that would have upgraded fine.
No change to the memory cap: nothing measured says 8Gi is short, and
resources_maximumis now settable per replica if it turns out to be.