Skip to content

eks-prow-build-cluster: Use Karpenter instead of cluster-autoscaler #5168

@xmudrii

Description

@xmudrii

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

Metadata

Metadata

Assignees

Labels

area/infraInfrastructure management, infrastructure design, code in infra/area/infra/awsIssues or PRs related to Kubernetes AWS infrastructurekind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/k8s-infraCategorizes an issue or PR as relevant to SIG K8s Infra.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions