Skip to content

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

@ronanww

Description

@ronanww

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

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions