收到此错误！！与服务器localhost:8080的连接被拒绝-您是否指定了正确的主机或端口？

Question

当我运行下面提到的命令＜code＞kubectl get po-n kube system＜/code＞时，我收到以下错误：：与服务器localhost:8080的连接被拒绝-您指定了正确的主机或端口吗？

Answer 1

我有一台K8S服务器运行良好，没有对其进行任何管理或更新更改。

有一天，它在重新启动后突然关闭。当您发出任何kubectl命令时，错误如下所示：

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

一个非常可能的原因是证书过期。

检查K8S证书：

admin@hostname:~$ sudo -i
[sudo] password for admin:
root@hostname:~#  kubeadm certs check-expiration
[check-expiration] Reading configuration from the cluster...
[check-expiration] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[check-expiration] Error reading configuration from the Cluster. Falling back to default configuration

CERTIFICATE                EXPIRES                  RESIDUAL TIME   CERTIFICATE AUTHORITY   EXTERNALLY MANAGED
admin.conf                 Jun 09, 2022 07:52 UTC   135d                                    no
apiserver                  Jun 09, 2022 07:52 UTC   135d            ca                      no
apiserver-etcd-client      Jun 09, 2022 07:52 UTC   135d            etcd-ca                 no
apiserver-kubelet-client   Jun 09, 2022 07:52 UTC   135d            ca                      no
controller-manager.conf    Jun 09, 2022 07:52 UTC   135d                                    no
etcd-healthcheck-client    Dec 31, 2021 04:11 UTC   **<invalid>**       etcd-ca                 no
etcd-peer                  Dec 31, 2021 04:11 UTC   **<invalid>**       etcd-ca                 no
etcd-server                Dec 31, 2021 04:11 UTC   **<invalid>**       etcd-ca                 no
front-proxy-client         Jun 09, 2022 07:52 UTC   135d            front-proxy-ca          no
scheduler.conf             Jun 09, 2022 07:52 UTC   135d                                    no

CERTIFICATE AUTHORITY   EXPIRES                  RESIDUAL TIME   EXTERNALLY MANAGED
ca                      Nov 03, 2030 13:32 UTC   8y              no
etcd-ca                 Nov 03, 2030 13:32 UTC   8y              no
front-proxy-ca          Nov 03, 2030 13:32 UTC   8y              no

我们可以看到一些证书是无效的。续订：

root@hostname:~# kubeadm certs renew etcd-healthcheck-client
[renew] Reading configuration from the cluster...
[renew] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[renew] Error reading configuration from the Cluster. Falling back to default configuration
certificate for liveness probes to healthcheck etcd renewed

root@hostname:~# kubeadm certs renew etcd-peer
[renew] Reading configuration from the cluster...
[renew] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[renew] Error reading configuration from the Cluster. Falling back to default configuration
certificate for etcd nodes to communicate with each other renewed

root@hostname:~# kubeadm certs renew etcd-server
[renew] Reading configuration from the cluster...
[renew] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[renew] Error reading configuration from the Cluster. Falling back to default configuration 
certificate for serving etcd renewed

Answer 2

嘿，我解决了我的错误：

尝试使用此GitHub线程并阅读整个评论并完全按照它所说的去做：

https://github.com/Hawaiideveloper/Infastructure-as-Code-Sample_Env/issues/15#issuecomment-811377749

事实证明，这是命令和对不兼容的 docker 版本的引用的组合，以及 Kubernetes 文档 03-31-2021 忘记提及的一些小事情。

Answer 3

localhost:8080是默认服务器，如果您的系统上没有kubeconfig（对于当前用户），则连接到该服务器。

按照链接页面上的说明进行操作。您将需要执行以下操作：

gCloud容器集群获取凭据[CLUSTER_NAME]