Minikube node tainted with k8s 1.9.6 - Pods Unschedulable as a result

[huguesalary]

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Please provide the following details:

Environment: mac os high sierra and mac os sierra

Minikube version : 0.28.2

• OS : mac os high sierra and mac os sierra
• VM Driver : hyperkit

What happened:

When creating a minikube cluster, the minikube node is tainted role.kubernetes.io/master:NoSchedule which prevents pods from being scheduled.

What you expected to happen:

In a minikube cluster, the only node is the minikube node. Minikube should remove the taint upon starting the cluster.

How to reproduce it (as minimally and precisely as possible):

minikube start \
--kubernetes-version v1.9.6 \
--vm-driver=hyperkit 

Anything else do we need to know:

I believe this taint is automatically added by k8s starting version >= 1.6

[dlorenc]

Ah, this looks like a bug :(

We started using the NoTaintMaster flag in kubeadm to avoid having to manually remove the taint, but this only became supported in 1.10.0. We'll need to keep supporting the old method of removing the taint until k8s 1.12 is released, and we drop 1.9 support.

[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

[viteksafronov]

the issue may be closed as fixed.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[viteksafronov]

/close

[k8s-ci-robot]

@viteksafronov: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.