-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't use latest stable version for minikube #856
Don't use latest stable version for minikube #856
Conversation
If you take a look at the CI log you'll find that the behavior your changes introduced is to download k8s 1.15 first, and then minikube installs k8s 1.14 again. This is a little redundant in my opinion - I think we could simply pin the k8s version to 1.14 for now(?) |
Why would you want to introduce a future bug? Every-time Kubernetes changes behavior you risk minikube breaking. The "working" Kubernetes version for minikube is hardcoded in minikube, and I think you should just minikube choose it's own version. The script downloads Also, this documented in my commit message, but just in case, I am repeating this again. kubeadm in its current version installes k8s in version 1.14.3. |
I have one nit on the link, then LGTM. We should have better mechanism to verify server-client skew, instead of tweaking minikube ad hoc |
Sometimes, minikube lags behind kubernetes which can lead to a breakage of the test suite, since minikube will fail to start with the latest kubernetes version. See for example [this issue](kubernetes/minikube#4371). This change defaults to leave the decision of which k8s version to use, to minikube itself. This is defined in: https://github.com/kubernetes/minikube/master/pkg/minikube/constants/constants.go However, if one really desires it is still possible to pass `--kubernetes-version=X.Y.Z` to minikube initialization start command via an environment variable before invoking the test suite: export $MINIKUBE_ARGS="--kubernetes-version=X.Y.Z" This allows ofcourse passing other flags to minikube also.
4e0332b
to
d7300db
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oz123, roycaihw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sometimes, minikube lags behind kubernetes which can lead
to a breakage of the test suite, since minikube will fail to start
with the latest kubernetes version.
See for example this issue.
This change defaults to leave the decision of which k8s version to use,
to minikube itself. This is defined in:
https://github.com/kubernetes/minikube/master/pkg/minikube/constants/constants.go
However, if one really desires it is still possible to pass
--kubernetes-version=X.Y.Z
to minikube initialization start command via an environment variable
before invoking the test suite:
export $MINIKUBE_ARGS="--kubernetes-version=X.Y.Z"
This allows ofcourse passing other flags to minikube also.