允许在Kubernetes主服务器上调度Pod吗? [英] Allow scheduling of pods on Kubernetes master?
问题描述
我使用通用安装脚本.它正在使用Kubernetes 1.5.4版运行当前的稳定发行版1298.6.0.
I set up Kubernetes on CoreOS on bare metal using the generic install scripts. It's running the current stable release, 1298.6.0, with Kubernetes version 1.5.4.
我们希望拥有一个高度可用的主设置，但是目前我们没有足够的硬件来专用于将三台服务器专门用作Kubernetes主服务器，因此我希望能够允许用户Pod被用作预定在Kubernetes主机上.我在/etc/systemd/system/kubelet.service中设置了--register-schedulable = true，但仍显示为SchedulingDisabled.
We'd like to have a highly available master setup, but we don't have enough hardware at this time to dedicate three servers to serving only as Kubernetes masters, so I would like to be able to allow user pods to be scheduled on the Kubernetes master. I set --register-schedulable=true in /etc/systemd/system/kubelet.service but it still showed up as SchedulingDisabled.
我试图添加设置以将节点包括为工作服务器，包括将工作服务器TLS证书添加到/etc/kubernetes/ssl，将这些设置添加到kubelet.service，添加/etc/kubernetes/worker-kubeconfig.yaml，指向这些证书，并将该信息添加到/etc/kubernetes/manifests/kube-proxy.yaml中.我将现有节点用作添加内容的模板.该节点在主节点的主机名下注册了另一个节点，然后它和原始主节点都显示为NotReady，SchedulingDisabled.
I tried to add settings for including the node as a worker, including adding worker TLS certs to /etc/kubernetes/ssl, adding those settings to kubelet.service, adding an /etc/kubernetes/worker-kubeconfig.yaml that pointed to those certs, and added that information to the /etc/kubernetes/manifests/kube-proxy.yaml. I used my existing nodes as a template for what to add. This registered another node under the master's hostname and then both it and the original master node showed up as NotReady,SchedulingDisabled.
这个问题表示应该可以在主节点上安排Pod，但是在此主题上我几乎找不到其他任何东西.
This question indicates that scheduling pods on the master node should be possible, but there is barely anything else that I can find on the subject.
推荐答案
如果您使用的是Kubernetes 1.7及更高版本:
If you are using Kubernetes 1.7 and above:
kubectl taint node mymasternode node-role.kubernetes.io/master:NoSchedule-
这篇关于允许在Kubernetes主服务器上调度Pod吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
