Simplify the names of the minikube machine drivers

[afbjorklund]

With the docker-machine drivers gone, there is no need for "kvm2" and "qemu2" any more.

And there is no need for "generic" or "none" either, the drivers can be renamed in minikube.

• kvm
• ssh (renamed from "generic")
• native (renamed from "none")
• qemu

	// AliasKVM is driver name alias for kvm2
	AliasKVM = "kvm"
	// AliasSSH is driver name alias for ssh
	AliasSSH = "generic"
	// AliasNative is driver name alias for None driver
	AliasNative = "native"
	// AliasQEMU is the driver name alias for qemu2
	AliasQEMU = "qemu"

• rename "none" driver to "native" #7772
• Fork the machine driver "generic" to minikube, prepare for renaming it #9583

Previously, kvm1 and qemu1 were the drivers used for docker-machine.

We tried to rename "kvm" to libvirt for sanity, but that name failed to stick.

• https://github.com/machine-drivers/docker-machine-driver-qemu

• https://github.com/machine-drivers/docker-machine-driver-libvirt

---

This change doesn't really affect anything that is user-facing, it is more of a refactoring.

Currently the real name is used as an alias, to the old libmachine-compatible driver name.

If changed, the situation would be more like the opposite (old name an alias, to the new name)

It is also not very important, both generic and none driver require special care in their setup...

[nirs]

kvm is the wrong name - both qemu and libvirt use kvm. The right name for the libvirt driver is libvirt. We can keep kvm and kvm2 as aliases do we don't break users.

[afbjorklund]

It originally came from here: https://github.com/dhiltgen/docker-machine-kvm (predating the qemu driver, but anyway)

[nirs]

If we want to be really correct, the name should be libvirt/kvm since libvirt supports also other drivers, but I think we have enough drivers ;-)

[afbjorklund]

If libvirt should ever support more accelerators than just kvm, I don't think the driver would be need to be forked for that?

But I am not going to rename anything beyond dropping docker-machine, after that all refactoring can happen in minikube

Also, without the external driver binaries it is easier to rename things...

Then the name is just in the minikube code, and not in program name.

[nirs]

If libvirt should ever support more accelerators than just kvm

https://libvirt.org/drivers.html#hypervisor-drivers

[afbjorklund]

I mean if the minikube libvirt driver ever needs another one

Like how qemu has kvm/hvf/whpx without different drivers

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[nirs]

/remove-lifecycle stale