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.

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

[Action] Cluster autoscaling/rightsizing #394

Open
1 of 6 tasks
JacobValdemar opened this issue Apr 22, 2024 · 3 comments
Open
1 of 6 tasks

[Action] Cluster autoscaling/rightsizing #394

JacobValdemar opened this issue Apr 22, 2024 · 3 comments

Comments

@JacobValdemar
Copy link

JacobValdemar commented Apr 22, 2024

Description

The set of nodes available in a cluster should be reasonable when considering the resource demand from workloads. It should not be so low that it reduces the quality of the service provided by the cluster's workloads (whatever that is). Nor should it be so high that it wastes compute resources. In fact, the set of nodes in a cluster should enable the cluster to meet its demands with the smallest environmental footprint possible.

Outcome

How do a Kubernetes Administrator fulfill the above description? The goal of this action item is to create a recommendation in our working document that helps a Kubernetes Administrator fulfill the above description.

To-Do

  • Research methods for manual rightsizing of cluster
  • Research tools available for automatic cluster rightsizing
  • Write down recommendation
  • Include relevant sources
  • Include background information

Code of Conduct

  • I agree to follow this project's Code of Conduct

Comments

If you are interested in collaborating on this recommendation with me, then feel free to comment on this issue. Everyone are welcome!

cc @xamebax

@thpang
Copy link

thpang commented Apr 25, 2024

Hi @JacobValdemar would like to participate. Thanks for starting this one. ;)

@JacobValdemar
Copy link
Author

Awesome to hear @thpang! 🤩 Any specific part of the To-Do you would like to participate in? 🙌 Also, I would love to see you at our next project meeting on Monday, 6th May, 13:00 CEST (11:00 UTC) if you can. I realize that it's a bit little early in the morning in your time zone 😅

@thpang
Copy link

thpang commented May 2, 2024

That's 7:00 AM here. I am usually up around 5:00-6:00 so should not be a problem. Dropping on my calendar now. I'll look over the to-do items as well. Thx again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants