cluster-autoscaler: terminating an instance does not mean there will be less desired instances #5420
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
while working on #5411 to fix #4095 I realized that the core bug is that we decrement the currentSize (aka asg desired size) when terminating an instance
... but that's now how aws works, terminating an instance does not decreases the desired size, it only makes a new instance come up
(#5411 is still useful since it reduces api call overhead and log spam)
partially reverts #1378
/cc @alam0rt @johanneswuerbach @aleksandra-malinowska
Which issue(s) this PR fixes:
Fixes #4095
Special notes for your reviewer:
Does this PR introduce a user-facing change?