Kubernetes kubeadm init由于拨打tcp 127.0.0.1:10248而失败：connect：连接被拒绝

Question

我正在尝试在vSphere私有云中设置一个非常简单的2节点k8s 1.13.3群集。 VM正在运行Ubuntu 18.04。防火墙已关闭以进行测试。但由于拒绝连接，初始化失败。除了端口被阻止之外还有其他可能导致此问题吗？我是k8s的新手，我正试图绕过这一切。

我在/ etc / kubernetes /中放置了一个vsphere.conf，如图所示。 https://gist.github.com/spstratis/0395073ac3ba6dc24349582b43894a77

我还创建了一个配置文件来指向我运行kubeadm init时。这是它的内容的例子。 https://gist.github.com/spstratis/086f08a1a4033138a0c42f80aef5ab40

当我运行sudo kubeadm init --config /etc/kubernetes/kubeadminitmaster.yaml时出现以下错误。

[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

检查sudo systemctl status kubelet告诉我kubelet正在运行。我暂时关闭了主VM上的防火墙以测试目的，以便我可以验证群集是否会自行启动。

   Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/kubelet.service.d
           └─10-kubeadm.conf
   Active: active (running) since Sat 2019-02-16 18:09:58 UTC; 24s ago
     Docs: https://kubernetes.io/docs/home/
 Main PID: 16471 (kubelet)
    Tasks: 18 (limit: 4704)
   CGroup: /system.slice/kubelet.service
           └─16471 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cloud-config=/etc/kubernetes/vsphere.conf --cloud-provider=vsphere --cgroup-driver=systemd --network-plugin=cni --pod-i

以下是一些额外的日志，显示与https://192.168.0.12:6443/的连接被拒绝。所有这些似乎都会导致kubelet失败并阻止init进程完成。

    Feb 16 18:10:22 k8s-master-1 kubelet[16471]: E0216 18:10:22.633721   16471 kubelet.go:2266] node "k8s-master-1" not found
    Feb 16 18:10:22 k8s-master-1 kubelet[16471]: E0216 18:10:22.668213   16471 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:453: Failed to list *v1.Node: Get https://192.168.0.12:6443/api/v1/nodes?fieldSelector=metadata.name%3Dk8s-master-1&limit=500&resourceVersion=0: dial tcp 192.168.0.1
Feb 16 18:10:22 k8s-master-1 kubelet[16471]: E0216 18:10:22.669283   16471 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/kubelet.go:444: Failed to list *v1.Service: Get https://192.168.0.12:6443/api/v1/services?limit=500&resourceVersion=0: dial tcp 192.168.0.12:6443: connect: connection refused
    Feb 16 18:10:22 k8s-master-1 kubelet[16471]: E0216 18:10:22.670479   16471 reflector.go:134] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://192.168.0.12:6443/api/v1/pods?fieldSelector=spec.nodeName%3Dk8s-master-1&limit=500&resourceVersion=0: dial tcp 192.1
    Feb 16 18:10:22 k8s-master-1 kubelet[16471]: E0216 18:10:22.734005   16471 kubelet.go:2266] node "k8s-master-1" not found

Answer 1

你不能使用bootstrap-kubeconfig来初始化master的kubelet，因为 - 正如你所经历的那样 - 它没有api服务器可以联系以生成它的私钥和证书。第二十二条军规。我大约80％肯定从kubelet args中移除--bootstrap-kubeconfig将有助于这种情况。我希望kubelet已经在/var/lib/kubelet/pki中拥有它的密钥和证书，所以这也许值得检查。

另外，假设您使用/etc/kubernetes/manifests目录运行apiserver和controllermanager，请确保staticPodPath:中的/var/lib/kubelet/config.yaml指向正确的目录。这不太可能是问题，但检查起来非常便宜。