compute: Add spec support for disabling LFC resizing #10132
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.
ref neondatabase/cloud#21731
Problem
When we manually override the LFC size for particular computes, autoscaling will typically undo that because vm-monitor will resize LFC itself.
So, we'd like a way to make vm-monitor not set LFC size — this actually already exists, if we just don't give vm-monitor a postgres connection string.
Summary of changes
Add a new field to the compute spec,
disable_lfc_resizing
. When set totrue
, we pass inNone
for its postgres connection string. That matches the configuration tested inneondatabase/autoscaling
CI.