eks-prow-build-cluster: Use Karpenter instead of cluster-autoscaler #5168
Labels
area/infra/aws
Issues or PRs related to Kubernetes AWS infrastructure
area/infra
Infrastructure management, infrastructure design, code in infra/
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/k8s-infra
Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone
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: