Skip to content

fix(spot): AWS placement score reaches config limits#753

Merged
adrianriobo merged 1 commit intoredhat-developer:mainfrom
adrianriobo:fix-752
Mar 26, 2026
Merged

fix(spot): AWS placement score reaches config limits#753
adrianriobo merged 1 commit intoredhat-developer:mainfrom
adrianriobo:fix-752

Conversation

@adrianriobo
Copy link
Copy Markdown
Collaborator

This commit uses a batch request to one single regions instead of multi region requests this avoids the config limits we are hitting, the commmit also introduces some forcedelete options to try to speed up delete process for spot instances

Fixes #752

This commit uses a batch request to one single regions instead of multi region requests this avoids the config limits we are hitting, the commmit also introduces some forcedelete options to try to speed up delete process for spot instances

Co-authored-by: Claude <noreply@anthropic.com>
Signed-off-by: Adrian Riobo <ariobolo@redhat.com>
@adrianriobo adrianriobo requested a review from ppitonak March 26, 2026 11:48
Copy link
Copy Markdown
Collaborator

@ppitonak ppitonak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to work fine

@adrianriobo adrianriobo merged commit 15b2960 into redhat-developer:main Mar 26, 2026
7 checks passed
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.

[error] Error getting data to pick the right spot instance type in AWS

2 participants