Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
Tracked by #5167
xmudrii opened this issue Apr 25, 2023 · 7 comments
Open
Tracked by #5167

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

xmudrii opened this issue Apr 25, 2023 · 7 comments
Assignees
@xmudrii
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
v1.30

Comments

@xmudrii
Copy link
Member

xmudrii commented Apr 25, 2023 •
edited

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 xmudrii mentioned this issue Apr 25, 2023
Closed
@xmudrii
Copy link
Member Author

xmudrii commented Apr 25, 2023

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 25, 2023
@xmudrii
Copy link
Member Author

xmudrii commented Apr 25, 2023

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

@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone Apr 25, 2023
@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. area/infra Infrastructure management, infrastructure design, code in infra/ area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Apr 25, 2023
@sbdtu5498
Copy link

/assign

@xmudrii xmudrii mentioned this issue Nov 15, 2023
Open
@xmudrii
Copy link
Member Author

xmudrii commented Nov 15, 2023

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

@xmudrii xmudrii mentioned this issue Dec 30, 2023
Closed
@xmudrii xmudrii mentioned this issue Jan 9, 2024
Merged
@xmudrii xmudrii mentioned this issue Jan 24, 2024
Merged
@xmudrii
Copy link
Member Author

xmudrii commented Feb 12, 2024

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

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.28, v1.30 Feb 12, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 12, 2024
@xmudrii
Copy link
Member Author

xmudrii commented May 20, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xmudrii xmudrii

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.
Projects
None yet
Milestone
v1.30
Development

No branches or pull requests
4 participants
@xmudrii @k8s-ci-robot @k8s-triage-robot @sbdtu5498