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

Bug in restarting a Minikube cluster created with "--cpus=no-limit --memory=no-limit" flags #17597

Closed
ronanww opened this issue Nov 9, 2023 · 0 comments · Fixed by #17598
Closed
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@ronanww
Copy link

ronanww commented Nov 9, 2023

What Happened?

A Minikube cluster was created with the flags --cpus=no-limit --memory=no-limit. This is what we observe in the Minikube config

cat ~/.minikube/profiles/minikube/config.json
{
...
	"Memory": 0,
	"CPUs": 0,
...
}

Then when restarting that cluster without the no-limit flags, the Minikube config seems to change and locks the memory and CPU to default values.

cat ~/.minikube/profiles/minikube/config.json
{
...
	"Memory": 32200,
	"CPUs": 2,
...
}

Attach the log file

Operating System

Other

Driver

Docker

@ronanww ronanww changed the title Bug in restarting a Minikube cluster with "--cpus=no-limit --memory=no-limit" flags Bug in restarting a Minikube cluster created with "--cpus=no-limit --memory=no-limit" flags Nov 9, 2023
@spowelljr spowelljr self-assigned this Nov 9, 2023
@spowelljr spowelljr added the kind/bug Categorizes issue or PR as related to a bug. label Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants