kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #5421 from kubernetes/tstromberg-patch-4 

Mention permanently pinning versions
pull/5427/head
Thomas Strömberg 2019-09-20 11:17:07 -07:00 committed by GitHub
parent 3e2958d7f4 0219ec7277
commit 01f399bc3f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
site/content/en/docs/Reference/Configuration/kubernetes.md
View File

@ -13,16 +13,20 @@ This flag is repeated, so you can pass it several times with several different v
## Selecting a Kubernetes version
minikube defaults to the latest stable version of Kubernetes. You may select a different Kubernetes release by using the `--kubernetes-version` flag, for example:
By default, minikube installs the latest stable version of Kubernetes that was available at the time of the minikube release. You may select a different Kubernetes release by using the `--kubernetes-version` flag, for example:
`minikube start --kubernetes-version=v1.11.10`
`minikube start --kubernetes-version=v1.11.10`
If you omit this flag, minikube will upgrade your cluster to the default version. If you would like to pin to a specific Kubernetes version across clusters, restarts, and upgrades to minikube, use:
`minikube config set kubernetes-version v1.11.0`
minikube follows the [Kubernetes Version and Version Skew Support Policy](https://kubernetes.io/docs/setup/version-skew-policy/), so we guarantee support for the latest build for the last 3 minor Kubernetes releases. When practical, minikube aims for the last 6 minor releases so that users can emulate legacy environments.
As of September 2019, this means that minikube supports and actively tests against the latest builds of:
* v1.16 (beta)
* v1.15 (default)
* v1.16 (default
* v1.15
* v1.14
* v1.13
* v1.12