kubernetes/minikube

minikube with kvm2 driver does not provide option to select storage pool

Open

#18,347 opened on Mar 10, 2024

View on GitHub
 (8 comments) (1 reaction) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
co/kvm2-driverhelp wantedkind/featurepriority/awaiting-more-evidence

Description

What Happened?

My 'local lab' uses zfs storage pool as default libvirt configured storage on the machine. However, when I use minikube to start k8s cluster locally it puts the kvm image file to ~/.minikube directory, which then creates 20GB .rawdisk file.

As there is --kvm-network option for kvm2 driver (for selecting the libvirt configured network), it would be neat to have the option to choose the storage pool where minikube would put all the images it's creating.

Attach the log file

No log file.

Operating System

Ubuntu

Driver

KVM2

Contributor guide

Tech stack
go
Domain
devopsinfrastructure
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Golibvirtminikube code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Look at the existing kvm network flag implementation in the kvm2 driver (likely in pkg/minikube/drivers/kvm2/). The storage pool option should follow a similar pattern: add a new CLI flag like kvm storage pool and pass it to the driver instance configuration. Use the libvirt go bindings to call libvirt's storage pool API to select or create the pool. The main code changes are in the kvm2 driver configuration and the minikube command handling.