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

kubernetes / k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

https://git.k8s.io/community/sig-k8s-infra

Apache License 2.0

693 stars 788 forks source link

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

Open xmudrii opened 1 year ago

xmudrii commented 1 year ago

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

xmudrii commented 1 year ago

/priority important-soon

xmudrii commented 1 year ago

/milestone v1.28 /sig k8s-infra /area infra /area infra/aws /kind cleanup

sbdtu5498 commented 1 year ago

/assign

xmudrii commented 8 months ago

@sbdtu5498 Are you still interested to work on this issue?

xmudrii commented 5 months ago

/unassign @sbdtu5498 /assign @xmudrii (@koksay will eventually work on this, I'll reassign it to him later) /milestone v1.30

k8s-triage-robot commented 2 months ago

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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was 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 commented 2 months ago

/remove-lifecycle stale