Skip to content

Conversation

@adrianriobo
Copy link
Collaborator

@adrianriobo adrianriobo commented Nov 19, 2025

Previously there was a fixed value to 8 on spot calculations, now if computeSizes are pass as param and the number of sizes is less than 8 it will use the len of compute sizes. This means now we will be able to use any number of compute sizes.
Fixes #622

Signed-off-by: Adrian Riobo [email protected]

@adrianriobo
Copy link
Collaborator Author

@ppitonak this should help you to reduce the number of machines set on ComputeSize now the minimum should be 3 from there you should not need such a long list

Copy link
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.

How/where is 3 enforced? In mapt or on API level?

@adrianriobo
Copy link
Collaborator Author

Yeah actually It is not imposed, I just tried with 2 and it worked..so let me change the commit message

Previously there was a fixed value to 8 on spot calculations, now if computeSizes are pass as param and the number of sizes is less than 8 it will use the len of compute sizes. This means now we will be able to use any number of compute sizes. Fix redhat-developer#622

Signed-off-by: Adrian Riobo <[email protected]>
@adrianriobo adrianriobo changed the title fix: Allow minimal computeSizes 3 as param for spot on AWS. fix: Allow any len for compute sizes param when asking for spot Nov 19, 2025
@adrianriobo adrianriobo merged commit ddb8f9b into redhat-developer:main Nov 20, 2025
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.

[bug] Too many required spot type machines when setting compute-sizes

2 participants