Allow pod schedule at Kubernet workshop?

Question

I installed Kubernetes on CoreOS on bare metal using standard installation scripts . It is running the current stable version 1298.6.0 with Kubernetes version 1.5.4.

We would like to have a highly accessible master setup, but now we don’t have enough equipment to select three servers for servicing only as Kubernetes masters, so I would like to be able to plan custom modules for Kubernetes Master. I set --register-schedulable = true to /etc/systemd/system/kubelet.service, but it still showed up as SchedulingDisabled.

I tried adding settings to enable the node as a working node, including adding TLS working certificates to / etc / kubernetes / ssl, adding these settings to kubelet.service, adding /etc/kubernetes/worker-kubeconfig.yaml, which points to these certificates and added this information to /etc/kubernetes/manifests/kube-proxy.yaml. I used my existing nodes as a template for what to add. This registered another node under the main host name, and then both it and the original main node were displayed as NotReady, SchedulingDisabled.

This question indicates that module planning on the main node should be possible, but I can hardly find anything on this issue.

Answer 1

If you are using Kubernetes 1.7 and above:

kubectl taint node mymasternode node-role.kubernetes.io/master:NoSchedule- 

Answer 2

I do not know why the main node is displayed as NotReady ; it shouldn't. Try kubectl describe node mymasternode to find out.

SchedulingDisabled is because the main node dedicated=master:NoSchedule

Run this command against all your wizards to remove the corruption:

 kubectl taint nodes mymasternode dedicated- 

To understand why this works, read about flogging and tolerance .

Answer 3

First, get the name of the master

 kubectl get nodes NAME STATUS ROLES AGE VERSION yasin Ready master 11d v1.13.4 

as we can see, there is one node named yasin and the role is master . If we want to use him as an employee, we must run

 kubectl taint nodes yasin node-role.kubernetes.io/master- 

Answer 4

For those who use cops on AWS. I wanted to enable Pods scheduling on master.

$ kubectl get nodes -owide gave me this output:

 NAME STATUS ... ... ip-1**-**-**-***.********.compute.internal Ready node ip-1**-**-**-***.********.master.internal Ready,SchedulingDisabled master ^^^^^^^^^^^^^^^^^^ ip-1**-**-**-***.********.compute.internal Ready node ... ... 

And $ kubectl describe nodes ip-1**-**-**-***.********.master.internal :

 ... ... Taints: <none> Unschedulable: true ... ^^^^ ... 

Wizard fix with this command:

$ kubectl patch node MASTER_NAME -p "{\"spec\":{\"unschedulable\":false}}"

worked for me, and Pods scheduling is now on.

Link: https://github.com/kubernetes/kops/issues/639#issuecomment-287015882

Answer 5

Use the command below to undo all wizards

 kubectl taint nodes --all node-role.kubernetes.io/master-