-
Notifications
You must be signed in to change notification settings - Fork 18
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
buffer replicas / resource request based on label #97
Comments
It sounds like related to So, we can extend this for the usecase so that the admin can specify which kind of Pods should get XXX % target at max. upperTargetResourceUtilization:
- labelSelector:
matchExpressions:
- key: nodepool
operator: In
values:
- spot
upperTargetResourceUtilization: 50%
- labelSelector:
matchExpressions:
- key: nodepool
operator: NotIn
values:
- spot
upperTargetResourceUtilization: 80% (after #98) |
Another usecase is some workloads, which have strict SLO, need to have additional buffer on the top of VPA recommendation. |
So, we need to have a new configuration for that: additionalBuffer:
- labelSelector:
matchExpressions:
- key: slo
operator: In
values:
- "super-high"
# either resources or resourceRatio should be configured.
resources:
cpu: 1 # 1 CPU is always added on the top of VPA recommendation.
memory: 1GB # 1GB memory is always added on the top of VPA recommendation.
resourcesRatio:
cpu: 10% # 10% CPU is always added on the top of VPA recommendation.
memory: 10% # 10% memory is always added on the top of VPA recommendation. |
Spot Nodes are very cheap but they have high risk of getting evicted at very short notice.
In order to use Spot VMs efficiently we can always have much higher replica count compared to running on OnDemand Nodes, this will solve 2 problems -
So suggestion is to run 25% (or even 50%) more replicas and ideal scenario if Deployment is running completely on Spot Nodes
The text was updated successfully, but these errors were encountered: