Skip to content

Minikube configuration management

minikube configuration management involves setting persistent parameters for the local Kubernetes cluster, such as the driver, memory allocation, and CPU limits.^[minikube.md]

Setting Configuration

Configuration values are managed using the minikube config set command.^[minikube.md] These settings are persistent, meaning they will be applied automatically to the cluster in future operations, though resource changes like memory typically require a stop and start cycle to take effect.^[minikube.md]

Driver Configuration

The driver determines the environment in which the Minikube container runs (e.g., Docker, VirtualBox). To set the Docker driver as the default, the following command is used:^[minikube.md]

[Minikube](<./minikube.md>) config set driver docker

Resource Allocation

Users can customize the amount of memory and CPUs allocated to the Minikube node.^[minikube.md] Changes to these settings require the cluster to be restarted (stopped and started) to be applied.^[minikube.md]

  • Set Memory: 
    [Minikube](<./minikube.md>) config set memory 8192
  • Set CPUs: 
    [Minikube](<./minikube.md>) config set cpus 4

Viewing Configuration

To verify the currently stored configuration values, use the view subcommand.^[minikube.md]

[Minikube](<./minikube.md>) config view

This will output a list of active settings, such as the configured memory, CPUs, and driver.^[minikube.md]

Runtime Overrides

It is possible to override the default configuration settings temporarily when starting a cluster by passing arguments directly to the minikube start command.^[minikube.md] For example, to start a cluster with specific resources that differ from the persistent config:

[Minikube](<./minikube.md>) start --cpus 6 --memory 12288

This allows for testing specific resource loads without changing the global default configuration.^[minikube.md]

Sources

^[minikube.md]