-
Notifications
You must be signed in to change notification settings - Fork 818
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
eks-prow-build-cluster: Use Karpenter instead of cluster-autoscaler #5168
Comments
/priority important-soon |
/milestone v1.28 |
/assign |
@sbdtu5498 Are you still interested to work on this issue? |
/unassign @sbdtu5498 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This is done! 🎉 |
@xmudrii: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
cluster-autoscaler doesn't support mixing different instance types. This is a problem because
r5ad.4xlarge
is way too expensive ($1.048/hr) and we might want to combine bigger and smaller instances (e.g. not all tests need such large instances).We also might want to consider mixing on-demand and spot instances for additional savings, which Karpenter would allow us to do.
/priority important-soon
The text was updated successfully, but these errors were encountered: