-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: mark spot as unavailable on LowPriorityQuota #93
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like the direction, left some comments.
May also want to rename this to something like "fix: mark spot as unavailable on LowPriorityQuota" (what actually happens after depends on other configuration)
Co-authored-by: Alex Leites <18728999+tallaxes@users.noreply.github.com>
implemented all that was mentioned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM👍
Fixes #91
Description
If spot capacity hits the spot regional cores count, karpenter should fall back onto on-demand. This PR adds that functionality
How was this change tested?
Does this change impact docs?
Release Note