我刚开始学习Kubernetes。我已经通过Kubernetes YUM存储库安装了带有SELinux禁用的kubectl，kubeadm和kubelet的CentOS 7.5。
但是，当我要启动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 Foundation课程，我不需要执行更多命令即可将第一个启动集群创建到VM中。
错了吗
Firewalld确实有进入防火墙的开放端口。 6443 / tcp和10248-10252
答案 0 :(得分：0)
您在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后，至少可以初始化集群。在我的集群中没有提供provide --node-name
答案 1 :(得分：0)
我建议按照官方documentation的指南引导Kubernetes集群。我已经进行了一些步骤，以在相同的CentOS版本CentOS Linux release 7.5.1804 (Core)上构建集群，并将与您共享它们，希望对您在安装过程中摆脱该问题有帮助。
首先擦除您当前的群集安装：
# kubeadm reset -f && rm -rf /etc/kubernetes/
添加Kubernetes存储库以进一步安装kubeadm，kubelet，kubectl：
[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设置为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标志传递给了{ {1}}命令。
为您的用户创建Kubernetes主目录并存储kubeadm init文件：
config安装Pod网络，在我的情况下是$ mkdir -p $HOME/.kube
$ sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
$ sudo chown $(id -u):$(id -g) $HOME/.kube/config
：
Flannel
最后检查Kubernetes核心Pod的状态：
$ kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml
$ kubectl get pods --all-namespaces如果您仍有任何疑问，请在此答案下方写下评论。