ubuntu - 连接到服务器 10.117.xxx.xxx :6443 was refused - did you specify the right host or port?

Question

我一直在尝试根据以下教程运行基本的 Kubernetes 集群 https://kubernetes.io/docs/setup/independent/install-kubeadm/

我从一个最新的 ubuntu 16.04 系统开始并安装了 docker。
wget -qO- https://get.docker.com/ | sed 's/docker-ce/docker-ce=18.06.3~ce~3-0~ubuntu/' | sh
之后我安装了 kubelet/Kubeadm 和 kubectl 模块

apt-get update && apt-get install -y apt-transport-https curl
curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
deb https://apt.kubernetes.io/ kubernetes-xenial main
EOF
apt-get update
apt-get install -y kubelet kubeadm kubectl
apt-mark hold kubelet kubeadm kubectl

确保交换等已关闭 sudo swapoff -a
使用 sudo kubeadm init 执行初始化

[init] Using Kubernetes version: v1.13.3
...
To start using your cluster
...
mkdir ...
You can now join any ...
...

我制作 .kube 文件夹和配置

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

kubectl cluster-info然后显示

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 10.117.xxx.xxx:6443 was refused - did you specify the right host or port?

在尝试了几次之后，我曾经收到过:

sudo kubectl cluster-info
Kubernetes master is running at https://10.117.xxx.xxx:6443
KubeDNS is running at https://10.117.xxx.xxx:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

但是一秒钟后，它又回到了被拒绝的权限

sudo kubectl cluster-info
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 10.117.xxx.xxx:6443 was refused - did you specify the right host or port?

我尝试了使用和不使用 sudo... 和 sudo kubectl get nodes也拒绝工作。

The connection to the server 10.117.xxx.xxx:6443 was refused - did you specify the right host or port?

我错过了什么，它不会连接？
ping 10.117.xxx.xxx工作正常，甚至ssh到此地址有效，并且是同一台服务器。

编辑
sudo systemctl restart kubelet.service显示集群上线但由于某种原因在几分钟内下线。

kubectl cluster-info
Kubernetes master is running at https://10.117.0.47:6443
KubeDNS is running at https://10.117.0.47:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
...
kubectl cluster-info

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 10.117.0.47:6443 was refused - did you specify the right host or port?

编辑2

进行完全重置并使用以下初始化后...

sudo kubeadm init --pod-network-cidr=10.244.0.0/16 

其次是

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/a70459be0084506e4ec919aa1c114638878db11b/Documentation/kube-flannel.yml

允许我安装 pod 网络插件，但只是短暂的。

clusterrole.rbac.authorization.k8s.io/flannel created
clusterrolebinding.rbac.authorization.k8s.io/flannel created
serviceaccount/flannel created
configmap/kube-flannel-cfg created
daemonset.extensions/kube-flannel-ds-amd64 created
daemonset.extensions/kube-flannel-ds-arm64 created
daemonset.extensions/kube-flannel-ds-arm created
daemonset.extensions/kube-flannel-ds-ppc64le created
daemonset.extensions/kube-flannel-ds-s390x created

kubectl cluster-info
Kubernetes master is running at https://10.117.xxx.xxx:6443
KubeDNS is running at https://10.117.xxx.xxx:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

➜  ~ kubectl cluster-info

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
The connection to the server 10.117.xxx.xxx:6443 was refused - did you specify the right host or port?

编辑3

删除所有 docker 镜像、容器等...然后使用 sudo systemctl restart kubelet.service 执行重启似乎做了几分钟的伎俩，但随后所有 docker 容器都被杀死并删除，没有任何信号。我如何查看这些容器的日志以找出它们被杀死的原因？

https://pastebin.com/wWSWXM31日志文件

Answer 1

我不知道“Kubernetes”的细节，但我可以解释你所看到的。

连接被拒绝不是权限被拒绝。这意味着:“我联系了该 IP 地址和端口的服务器，但该端口上没有运行任何服务器。”

所以....您将不得不转到远程系统(您一直调用 10.117.xxx.xxx 的系统)并仔细检查服务器是否正在运行。以及在什么端口上。

例如，“netstat -a”工具将列出所有打开的端口和连接。您应该将监听服务器视为

tcp        0      0 0.0.0.0:9090            0.0.0.0:*               LISTEN     

在我的情况下，它正在监听端口 9090。您正在寻找一个带有 6443 的条目。它可能不会存在，因为“连接被拒绝”已经告诉您了。您需要启动应该提供该服务的服务器进程并注意错误。如果您在终端上看不到/var/log/syslog 中的错误，请检查它们。