-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Minikube 1.7.0 will not start with TaintNodesByCondition=false feature gate #6516
Comments
Thank you for the excellent bug report. I tried this with HEAD, as well as minikube v1.7.0-beta.1 and Kubernetes v1.7.0, and ran into this error, shown by the kubelet logs:
If I specify I noticed from your logs, that at least some of your components are v1.15.6, which should work. Could it be possible that minikube was trying to upgrade your cluster to v1.17.x? It would be helpful if you could share the output of |
Oh. Sorry. Here's the run again, this time though I've done the following:
Starting it like so:
The output produced is:
I still have the same issue:
And just in case here's
|
This seems to be resolved as of Minikube version 1.7.2 |
We have a script that stands up local development environments that sets the
TaintNodesByCondition=false
feature gate.For all previous versions of Minikube up to and including version 1.6.2 has worked fine.
For Minikube 1.7.0 for some reason a taint is being applied to the Minikube node, and critical pods in the kube-system area such as coredns will not start due to it.
The reason we are setting this feature gate is described in our GIT commit for the setup script as follows:
It is strange that using this flag to disable taints causes a taint to be applied to the node.
If I remove the
--feature-gates TaintNodesByCondition=false
start up option then Minikube 1.7.0 starts without issue, but then we'll get the undesirable behaviour in our local development environments again.The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version:
The text was updated successfully, but these errors were encountered: