错误标记大师：等待条件超时[kubernetes]
error marking master: timed out waiting for the condition [kubernetes]
刚开始学习Kubernetes。我安装了 CentOS 7.5，SELinux 通过 Kubernetes YUM 存储库禁用了 kubectl、kubeadm 和 kubelet。
但是，当我要启动一个kubeadm init命令时。我收到此错误消息：
[init] using Kubernetes version: v1.12.2
[preflight] running pre-flight checks
[WARNING Firewalld]: firewalld is active, please ensure ports [6443 10250] are open or your cluster may not function correctly
[preflight/images] Pulling images required for setting up a Kubernetes cluster
[preflight/images] This might take a minute or two, depending on the speed of your internet connection
[preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[preflight] Activating the kubelet service
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Generated etcd/ca certificate and key.
[certificates] Generated etcd/peer certificate and key.
[certificates] etcd/peer serving cert is signed for DNS names [vps604805.ovh.net localhost] and IPs [51.75.201.75 127.0.0.1 ::1]
[certificates] Generated apiserver-etcd-client certificate and key.
[certificates] Generated etcd/server certificate and key.
[certificates] etcd/server serving cert is signed for DNS names [vps604805.ovh.net localhost] and IPs [127.0.0.1 ::1]
[certificates] Generated etcd/healthcheck-client certificate and key.
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [vps604805.ovh.net kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 51.75.201.75]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] valid certificates and keys now exist in "/etc/kubernetes/pki"
[certificates] Generated sa key and public key.
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests"
[init] this might take a minute or longer if the control plane images have to be pulled
[apiclient] All control plane components are healthy after 26.003496 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.12" in namespace kube-system with the configuration for the kubelets in the cluster
[markmaster] Marking the node vps604805.ovh.net as master by adding the label "node-role.kubernetes.io/master=''"
[markmaster] Marking the node vps604805.ovh.net as master by adding the taints [node-role.kubernetes.io/master:NoSchedule]
error marking master: timed out waiting for the condition
根据 Linux 基础课程，我不需要执行更多命令来在我的 VM 中创建我的第一个启动集群。
错了？
Firewalld 确实打开了防火墙端口。 6443/tcp 和 10248-10252
您在 kubernetes 中遇到了以下问题
https://github.com/kubernetes/kubeadm/issues/1092
解决方法是提供--node-name=<hostname>。只需浏览以上票证即可了解更多信息。希望这有帮助
编辑：
我在 kubeadm-1.10.0 中有同样的问题
从 /etc/systemd/system/kubelet.service.d/10-kubeadm.conf 文件中删除 --hostname-override 后，至少能够初始化集群。没有在我的集群中提供 --node-name
我会按照官方 documentation 的指导推荐 bootstrap Kubernetes 集群。我已经在同一个CentOS版本CentOS Linux release 7.5.1804 (Core)上进行了一些构建集群的步骤，并将与您分享，希望它可以帮助您解决安装过程中的问题。
首先擦除您当前的集群安装：
# kubeadm reset -f && rm -rf /etc/kubernetes/
为进一步 kubeadm、kubelet、kubectl 安装添加 Kubernetes 存储库：
[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
exclude=kube*
EOF
检查SELinux是否处于宽容模式：
# getenforce
Permissive
确保 net.bridge.bridge-nf-call-iptables 在您的 sysctl 中设置为 1:
# cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system
安装所需的 Kubernetes 组件并启动服务：
# yum update && yum upgrade && yum install -y docker kubelet kubeadm kubectl --disableexcludes=kubernetes
# systemctl start docker kubelet && systemctl enable docker kubelet
通过kubeadm部署集群：
kubeadm init --pod-network-cidr=10.244.0.0/16
我更喜欢在我的集群中安装 Flannel 作为主要 CNI，尽管正确 Pod network 安装有一些先决条件，我已经通过了 --pod-network-cidr=10.244.0.0/16 标志到 kubeadm init 命令。
为您的用户创建 Kubernetes 主目录并存储 config 文件：
$ mkdir -p $HOME/.kube
$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
$ sudo chown $(id -u):$(id -g) $HOME/.kube/config
安装 Pod 网络，在我的例子中是 Flannel:
$ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml
最后检查 Kubernetes 核心 Pods 状态：
$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-576cbf47c7-4x7zq 1/1 Running 0 36m
kube-system coredns-576cbf47c7-666jm 1/1 Running 0 36m
kube-system etcd-centos-7-5 1/1 Running 0 35m
kube-system kube-apiserver-centos-7-5 1/1 Running 0 35m
kube-system kube-controller-manager-centos-7-5 1/1 Running 0 35m
kube-system kube-flannel-ds-amd64-2bmw9 1/1 Running 0 33m
kube-system kube-proxy-pcgw8 1/1 Running 0 36m
kube-system kube-scheduler-centos-7-5 1/1 Running 0 35m
如果您还有任何疑问，请在此答案下方写下评论。
在某些系统中，特别是较旧的 Ubuntu 版本，可以通过获取稍旧版本的 k8s 主组件来解决此问题，即 kubectl、kubeadm 和 kubelet.
为此，删除您当前的设置：
sudo kubeadm reset
sudo rm -rf /etc/kubernetes
sudo apt-get remove kubectl kubeadm kubelet
然后，重新安装版本 1.20.2-00:
sudo apt-get install -y kubelet=1.20.2-00 kubeadm=1.20.2-00 kubectl=1.20.2-00
刚开始学习Kubernetes。我安装了 CentOS 7.5，SELinux 通过 Kubernetes YUM 存储库禁用了 kubectl、kubeadm 和 kubelet。
但是，当我要启动一个kubeadm init命令时。我收到此错误消息：
[init] using Kubernetes version: v1.12.2
[preflight] running pre-flight checks
[WARNING Firewalld]: firewalld is active, please ensure ports [6443 10250] are open or your cluster may not function correctly
[preflight/images] Pulling images required for setting up a Kubernetes cluster
[preflight/images] This might take a minute or two, depending on the speed of your internet connection
[preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[preflight] Activating the kubelet service
[certificates] Generated front-proxy-ca certificate and key.
[certificates] Generated front-proxy-client certificate and key.
[certificates] Generated etcd/ca certificate and key.
[certificates] Generated etcd/peer certificate and key.
[certificates] etcd/peer serving cert is signed for DNS names [vps604805.ovh.net localhost] and IPs [51.75.201.75 127.0.0.1 ::1]
[certificates] Generated apiserver-etcd-client certificate and key.
[certificates] Generated etcd/server certificate and key.
[certificates] etcd/server serving cert is signed for DNS names [vps604805.ovh.net localhost] and IPs [127.0.0.1 ::1]
[certificates] Generated etcd/healthcheck-client certificate and key.
[certificates] Generated ca certificate and key.
[certificates] Generated apiserver certificate and key.
[certificates] apiserver serving cert is signed for DNS names [vps604805.ovh.net kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 51.75.201.75]
[certificates] Generated apiserver-kubelet-client certificate and key.
[certificates] valid certificates and keys now exist in "/etc/kubernetes/pki"
[certificates] Generated sa key and public key.
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
[controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
[controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
[controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
[init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests"
[init] this might take a minute or longer if the control plane images have to be pulled
[apiclient] All control plane components are healthy after 26.003496 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.12" in namespace kube-system with the configuration for the kubelets in the cluster
[markmaster] Marking the node vps604805.ovh.net as master by adding the label "node-role.kubernetes.io/master=''"
[markmaster] Marking the node vps604805.ovh.net as master by adding the taints [node-role.kubernetes.io/master:NoSchedule]
error marking master: timed out waiting for the condition
根据 Linux 基础课程，我不需要执行更多命令来在我的 VM 中创建我的第一个启动集群。
错了？
Firewalld 确实打开了防火墙端口。 6443/tcp 和 10248-10252
您在 kubernetes 中遇到了以下问题
https://github.com/kubernetes/kubeadm/issues/1092
解决方法是提供--node-name=<hostname>。只需浏览以上票证即可了解更多信息。希望这有帮助
编辑： 我在 kubeadm-1.10.0 中有同样的问题 从 /etc/systemd/system/kubelet.service.d/10-kubeadm.conf 文件中删除 --hostname-override 后，至少能够初始化集群。没有在我的集群中提供 --node-name
我会按照官方 documentation 的指导推荐 bootstrap Kubernetes 集群。我已经在同一个CentOS版本CentOS Linux release 7.5.1804 (Core)上进行了一些构建集群的步骤，并将与您分享，希望它可以帮助您解决安装过程中的问题。
首先擦除您当前的集群安装：
# kubeadm reset -f && rm -rf /etc/kubernetes/
为进一步 kubeadm、kubelet、kubectl 安装添加 Kubernetes 存储库：
[kubernetes]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
exclude=kube*
EOF
检查SELinux是否处于宽容模式：
# getenforce
Permissive
确保 net.bridge.bridge-nf-call-iptables 在您的 sysctl 中设置为 1:
# cat <<EOF > /etc/sysctl.d/k8s.conf
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
EOF
sysctl --system
安装所需的 Kubernetes 组件并启动服务：
# yum update && yum upgrade && yum install -y docker kubelet kubeadm kubectl --disableexcludes=kubernetes
# systemctl start docker kubelet && systemctl enable docker kubelet
通过kubeadm部署集群：
kubeadm init --pod-network-cidr=10.244.0.0/16
我更喜欢在我的集群中安装 Flannel 作为主要 CNI，尽管正确 Pod network 安装有一些先决条件，我已经通过了 --pod-network-cidr=10.244.0.0/16 标志到 kubeadm init 命令。
为您的用户创建 Kubernetes 主目录并存储 config 文件：
$ mkdir -p $HOME/.kube
$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
$ sudo chown $(id -u):$(id -g) $HOME/.kube/config
安装 Pod 网络，在我的例子中是 Flannel:
$ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml
最后检查 Kubernetes 核心 Pods 状态：
$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-576cbf47c7-4x7zq 1/1 Running 0 36m
kube-system coredns-576cbf47c7-666jm 1/1 Running 0 36m
kube-system etcd-centos-7-5 1/1 Running 0 35m
kube-system kube-apiserver-centos-7-5 1/1 Running 0 35m
kube-system kube-controller-manager-centos-7-5 1/1 Running 0 35m
kube-system kube-flannel-ds-amd64-2bmw9 1/1 Running 0 33m
kube-system kube-proxy-pcgw8 1/1 Running 0 36m
kube-system kube-scheduler-centos-7-5 1/1 Running 0 35m
如果您还有任何疑问，请在此答案下方写下评论。
在某些系统中，特别是较旧的 Ubuntu 版本，可以通过获取稍旧版本的 k8s 主组件来解决此问题，即 kubectl、kubeadm 和 kubelet.
为此，删除您当前的设置：
sudo kubeadm reset
sudo rm -rf /etc/kubernetes
sudo apt-get remove kubectl kubeadm kubelet
然后，重新安装版本 1.20.2-00:
sudo apt-get install -y kubelet=1.20.2-00 kubeadm=1.20.2-00 kubectl=1.20.2-00