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

timeToK8s: Give minikube the same amount of memory as kind and k3d #11650

Closed
sharifelgamal opened this issue Jun 14, 2021 · 1 comment
Closed

timeToK8s: Give minikube the same amount of memory as kind and k3d #11650

sharifelgamal opened this issue Jun 14, 2021 · 1 comment
Assignees
@spowelljr
Labels
kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
1.23.0

Comments

@sharifelgamal
Copy link
Collaborator

sharifelgamal commented Jun 14, 2021 •
edited by spowelljr
Loading

By default, kind and k3d do not have a set limit on the amount of memory they use. minikube by default decides how much memory to allocate, this difference in available memory puts minikube at a disadvantage. Give minikube unlimited or a large amount of memory during the time-to-k8s benchmark to make the results more comparable.
@sharifelgamal sharifelgamal added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/process Process oriented issues, like setting up CI labels Jun 14, 2021
@sharifelgamal sharifelgamal added this to the 1.22.0-candidate milestone Jun 14, 2021
@spowelljr
Copy link
Member

In-progress

@spowelljr spowelljr mentioned this issue Jun 17, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spowelljr spowelljr

Labels
kind/process Process oriented issues, like setting up CI priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
1.23.0
Development

No branches or pull requests
2 participants
@sharifelgamal @spowelljr