Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Missing toleration prevents controller manager from being scheduled on master #139

Closed
Ratedev opened this issue Oct 22, 2018 · 2 comments
Closed

Missing toleration prevents controller manager from being scheduled on master #139

Ratedev opened this issue Oct 22, 2018 · 2 comments

Comments

@Ratedev
Copy link

Ratedev commented Oct 22, 2018

Kubernetes Version: 1.12.1
When setting --cloud-provider=external on the kubelet on the master node, the master gets the following taint: node.kubernetes.io/not-ready:NoSchedule

please add following tolaration to the controller manager:

  • key: "node.kubernetes.io/not-ready"
    effect: NoSchedule
@andrewsykim
Copy link
Contributor

The node taint corresponding to --cloud-provider=external is actually node.cloudprovider.kubernetes.io/uninitialized (see here). node.kubernetes.io/not-ready taint is usually due to some other issues on the node, does kubectl describe node say anything useful?

@Ratedev
Copy link
Author

Ratedev commented Oct 23, 2018 •
edited

Ah, yes. Sorry.
It was a network plugin error

@Ratedev Ratedev closed this as completed Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ratedev @andrewsykim