eks-prow-build-cluster: Costs optimization

[xmudrii]

We didn't pay much attention to optimizing costs while building eks-prow-build-cluster, but we should eventually do so. There are some steps that we can take to reduce costs short-term and long-term.

Tasks

Preview Give feedback

1. eks-prow-build-cluster: Use Karpenter instead of cluster-autoscaler #5168
   area/infra area/infra/aws kind/cleanup lifecycle/stale priority/important-soon sig/k8s-infra +6
   
2. eks-prow-build-cluster: Reconsider instance type selection #5066
   kind/cleanup lifecycle/frozen sig/k8s-infra sig/testing +4
3. Mutate eks-prow-build-cluster image pulls to use ECR #4928
   lifecycle/frozen sig/k8s-infra +2
4. Reduce spent either on SSDs or provisioned IOPS
5. Look into reducing spent on NAT Gateway and other networking related costs

/priority important-longterm

[xmudrii]

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

[k8s-triage-robot]

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]

/remove-lifecycle stale

[xmudrii]

We don't need this issue
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

We don't need this issue
/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/test-infra repository.