You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
What happened: spotPrice does not seem to behave properly. When we set it either to the value higher than the current price or lower than the current price, the instance always gets created and is always marked as lifecycle=normal in AWS EC2 view, while instance-manager claims it is lifecycle=spot.
What you expected to happen:
InstanceGroup is Ready
k8s node becomes NotReady because the spot Price does not match the current price
How to reproduce it (as minimally and precisely as possible):
create InstanceGroup with spotPrice="0.0001" and instanceType=m5.xlarge
check the EC2 type and Spot Requests in AWS console (EC2 type is normal and Spot Requests are empty)
There might be a problem the with setting of lifecycle=spot in this case. I think the current logic depends on whether a spot price is set or not, and not whether instances are actually switched to spot.
In the case of using spot recommendations with minion manager that works fine since the price is available, but if someone just sets a spotPrice which is not available the result would be lifecycle=spot and it cannot switch because the price is not available.
My recommendation for now is to either use spot recommendations via minion-manager or switch to spot via LaunchTemplate/Mixed Instance Policies which is a more automated mechanism via AWS.
Thank you guys for your thoughts!
Yes, it worked with MixedInstancePolicies or with minion-manager but was curious if it is expected to work for spotPrice.
I'll gladly collaborate and help in introducing a better logic here (or at least fixing the documentation explaining the desired logic).
Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
What happened:
spotPrice
does not seem to behave properly. When we set it either to the value higher than the current price or lower than the current price, the instance always gets created and is always marked aslifecycle=normal
in AWS EC2 view, whileinstance-manager
claims it islifecycle=spot
.What you expected to happen:
Ready
NotReady
because the spot Price does not match the current priceHow to reproduce it (as minimally and precisely as possible):
spotPrice="0.0001"
andinstanceType=m5.xlarge
normal
and Spot Requests are empty)Anything else we need to know?:
Documentation is a bit misleading saying that
spotPrice
is theminimal
spot price.As per https://github.com/keikoproj/instance-manager/blob/master/docs/EKS.md#eksconfiguration
Environment:
Other debugging information (if applicable):
The text was updated successfully, but these errors were encountered: