kubernetes
eks-prow-build-cluster: Use Karpenter instead of cluster-autoscaler
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
/unassign @sbdtu5498 /assign @xmudrii (@koksay will eventually work on this, I'll reassign it to him later) /milestone v1.30
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@xmudrii: Closing this issue.
In response to this:
This is done! 🎉 /close
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.
