kubernetes/minikube

Make the available drivers section a bit clearer

Open

#9,803 opened on Nov 29, 2020

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Go (31,799 stars) (5,222 forks)batch import
help wantedkind/documentationlifecycle/frozenpriority/backlog

Description

Currently it is a bit unclear what you actually need:

Container or virtual machine manager, such as: Docker, Hyperkit, Hyper-V, KVM, Parallels, Podman, VirtualBox, or VMWare

This mixes containers and virtual machines etc.

We need to make some kind of distinction between local drivers Docker and Podman, and remote drivers Docker and Podman.

And try to explain how it is related to the hypervisors, Hyperkit, Hyper-V, KVM (Libvirt), Parallels, VMware and the --vm=true

Beyond separating Docker Engine and Docker Desktop.

Contributor guide

Tech stack
go
Domain
documentation
Issue type
documentation
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.
half day
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
Basic knowledge of Docker/Podman
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The current documentation at https://minikube.sigs.k8s.io/docs/drivers/ likely needs restructuring. Investigate how drivers are categorized (local vs remote) and propose a clearer separation. Look at existing comments for suggestions on formatting and wording. Consider adding a table explaining the relationship between drivers, hypervisors, and the vm flag.