Add support for --kubernetes-version=(latest|stable) aliases

[tstromberg]

As proposed by @robrich in #6122

As I mentioned there, minikube does not yet support latest or stableversion aliases, but it would be trivial to add. If you or anyone else is interested in making this work, add a check forparamVersion == "stable"` here:

minikube/cmd/minikube/cmd/start.go

Line 1127 in 56c72e2

if paramVersion == "" { // if the user did not specify any version then ...

We currently store the stable and latest versions as constants that you can refer to.

[robrich]

I see versions defined in

minikube/pkg/minikube/constants/constants.go

Lines 67 to 74 in b6ff7ba

	// DefaultKubernetesVersion is the default kubernetes version
	var DefaultKubernetesVersion = "v1.17.0"
	// NewestKubernetesVersion is the newest Kubernetes version to test against
	var NewestKubernetesVersion = "v1.17.0"
	// OldestKubernetesVersion is the oldest Kubernetes version to test against
	var OldestKubernetesVersion = "v1.11.10"

but it's default, newest, and oldest. Did I miss stable? I'm guessing as of this writing, stable would be 1.16.4 and latest would be 1.18.0-alpha.1 (Mirroring https://github.com/kubernetes/kubernetes/releases). Is this right?

[tstromberg]

Default is stable.

Newest should be updated to v1.18.0-alpha.1.

[ghost]

/assign
Hi, I would like to work on that one

[tstromberg]

@ths-laurent - sounds great! Feel free to ask here for any clarifications necessary to implement this feature. :)

[ghost]

Thanks :). At first I wasn't sure if the NewestKubernetesVersion constant had to be updated but re-reading the comments helped clarifying that.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[linkvt]

Seems that the user deleted his account, the PR had also no activity despite it seems to be fixed. /assign

[linkvt]

/remove-lifecycle stale

[linkvt]

/assign