kubeadm init之后kubectl get nodes

最新推荐文章于 2025-05-11 14:56:51 发布

原创最新推荐文章于 2025-05-11 14:56:51 发布 · 2.6k 阅读

0 ·

CC 4.0 BY-SA版权

DOCKER 专栏收录该内容

8 篇文章

订阅专栏

本文介绍了解决在使用kubectl命令时遇到的连接错误问题的方法。通过执行特定的配置文件复制和权限更改步骤，确保kubectl能够正确地与集群进行通信。此外，还提供了处理由于缺少内核模块而导致的问题的解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

kubeadm init之后kubectl get nodes 提示“The connection to the server localhost:8080 was refused - did you specify the right host or port?”

did you run below commands after kubeadm init

To start using your cluster, you need to run (as a regular user):

sudo cp /etc/kubernetes/admin.conf $HOME/
sudo chown $(id -u):$(id -g) $HOME/admin.conf
export KUBECONFIG=$HOME/admin.conf （关键一条）

----------------------------------------------------

[root@192.168.127.132 yum.repos.d]#kubeadm join 192.168.127.134:6443 --token tzb8fz.q3bqdwxmlht7gebj --discovery-token-ca-cert-hash sha256:59215d1229bd7cab2bc44872a34feba2055d7e7ed62b518415343001d3723e38
[preflight] running pre-flight checks
[WARNING RequiredIPVSKernelModulesAvailable]: the IPVS proxier will not be used, because the following required kernel modules are not loaded: [ip_vs_rr ip_vs_wrr ip_vs_sh ip_vs] or no builtin kernel ipvs support: map[ip_vs_sh:{} nf_conntrack_ipv4:{} ip_vs:{} ip_vs_rr:{} ip_vs_wrr:{}]
you can solve this problem with following methods:
1. Run 'modprobe -- ' to load missing kernel modules;
2. Provide the missing builtin kernel ipvs support

[WARNING Service-Docker]: docker service is not enabled, please run 'systemctl enable docker.service'
I0802 01:56:29.715075 1849 kernel_validator.go:81] Validating kernel version
I0802 01:56:29.715268 1849 kernel_validator.go:96] Validating kernel config
[discovery] Trying to connect to API Server "192.168.127.134:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://192.168.127.134:6443"
[discovery] Requesting info from "https://192.168.127.134:6443" again to validate TLS against the pinned public key
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "192.168.127.134:6443"
[discovery] Successfully established connection with API Server "192.168.127.134:6443"
[kubelet] Downloading configuration for the kubelet from the "kubelet-config-1.11" ConfigMap in the kube-system namespace
[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[preflight] Activating the kubelet service
[tlsbootstrap] Waiting for the kubelet to perform the TLS Bootstrap...
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "192.168.127.132" as an annotation

This node has joined the cluster:
* Certificate signing request was sent to master and a response
was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the master to see this node join the cluster.
[root@192.168.127.132 yum.repos.d]#modprobe ip_vs_rr
[root@192.168.127.132 yum.repos.d]#modprobe ip_vs_wrr
[root@192.168.127.132 yum.repos.d]#modprobe ip_vs_sh
[root@192.168.127.132 yum.repos.d]#modprobe ip_vs