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

Request for ability to control memory/cpu resource allocated to nodes #2395

Closed
zephinzer opened this issue Jul 29, 2021 · 2 comments
Closed
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@zephinzer
Copy link

What would you like to be added: Ability to specify memory/cpu values for each node

Why is this needed: Having this would enable localised testing of workload behaviour mimicing a real cluster's resources (example question that can be answered: does OOM happen given we are using 120% memory based on limits but 80% based on requests?)

Haven't dug into how kind works so I'm not too sure how complex this will be but the Docker daemon seems to allow for specifying of resources so it could be adding configuration during this step?

If it's in line with kind's roadmap, I can help with this-

@zephinzer zephinzer added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 29, 2021
@zephinzer
Copy link
Author

Just found #877, which seems to be a duplicate, feel free to close-

@BenTheElder BenTheElder added the triage/duplicate Indicates an issue is a duplicate of other open issue. label Jul 29, 2021
@BenTheElder
Copy link
Member

This is unfortunately trickier than you might hope to do correctly at the moment and not something I personally can justify focusing on at the moment. If someone proposes a workable plan in #877 I will do my best to help see it through. I think most/all? of the kind maintainers are currently burning all cycles maintaining the project and doing their "real" work on other projects 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Development

No branches or pull requests

2 participants