After creating the cluster in Kubernetes, the following error occurs after 1 minute of execution
The connection to the server 192.168.1.7:6443 was refused - did you specify the right host or port?
The steps I took to install Kubernetes are as follows:
sudo swapoff -a
sudo ufw disbale
sudo systemctl enbale containerd
sudo systemctl start containerd
sudo kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=192.168.1.7
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-565d847f94-cz525 0/1 Pending 0 2d22h
coredns-565d847f94-rwl2h 0/1 Pending 0 2d22h
etcd-master 1/1 Running 699 (2m42s ago) 2d22h
kube-apiserver-master 1/1 Running 665 (6m35s ago) 2d22h
kube-controller-manager-master 1/1 Running 750 (69s ago) 2d22h
kube-proxy-h8dtw 0/1 CrashLoopBackOff 610 (29s ago) 2d22h
kube-scheduler-master 1/1 Running
kubectl get events --all-namespaces --sort-by='.metadata.creationTimestamp'
default 60m Normal RegisteredNode node/master Node master event: Registered Node master in Controller
kube-system 31m Warning BackOff pod/kube-apiserver-master Back-off restarting failed container
default 4m20s Normal Starting node/master Starting kubelet.
default 4m20s Warning InvalidDiskCapacity node/master invalid capacity 0 on image filesystem
default 4m20s Normal NodeHasSufficientMemory node/master Node master status is now: NodeHasSufficientMemory
default 4m20s Normal NodeHasNoDiskPressure node/master Node master status is now: NodeHasNoDiskPressure
default 4m20s Normal NodeHasSufficientPID node/master Node master status is now: NodeHasSufficientPID
default 4m20s Normal NodeAllocatableEnforced node/master Updated Node Allocatable limit across pods
kube-system 65s Normal Killing pod/kube-controller-manager-master Stopping container kube-controller-manager
kube-system 2m21s Normal Killing pod/kube-scheduler-master Stopping container kube-scheduler
kube-system 3m45s Normal Created pod/etcd-master Created container etcd
kube-system 63s Normal SandboxChanged pod/kube-controller-manager-master Pod sandbox changed, it will be killed and re-created.
kube-system 3m45s Normal Started pod/etcd-master Started container etcd
kube-system 4m19s Normal Pulled pod/kube-apiserver-master Container image "registry.k8s.io/kube-apiserver:v1.25.0" already present on machine
kube-system 3m45s Normal Pulled pod/etcd-master Container image "registry.k8s.io/etcd:3.5.4-0" already present on machine
kube-system 4m16s Normal Created pod/kube-apiserver-master Created container kube-apiserver
kube-system 4m16s Normal Started pod/kube-apiserver-master Started container kube-apiserver
kube-system 2m17s Normal SandboxChanged pod/kube-scheduler-master Pod sandbox changed, it will be killed and re-created.
kube-system 3m52s Normal Pulled pod/kube-controller-manager-master Container image "registry.k8s.io/kube-controller-manager:v1.25.0" already present on machine
kube-system 44s Normal Created pod/kube-proxy-h8dtw Created container kube-proxy
kube-system 45s Normal Pulled pod/kube-proxy-h8dtw Container image "registry.k8s.io/kube-proxy:v1.25.0" already present on machine
kube-system 114s Normal Started pod/kube-scheduler-master Started container kube-scheduler
kube-system 3m52s Normal Created pod/kube-controller-manager-master Created container kube-controller-manager
kube-system 114s Normal Created pod/kube-scheduler-master Created container kube-scheduler
kube-system 115s Normal Pulled pod/kube-scheduler-master Container image "registry.k8s.io/kube-scheduler:v1.25.0" already present on machine
kube-system 3m51s Normal Started pod/kube-controller-manager-master Started container kube-controller-manager
kube-system 3m42s Warning Unhealthy pod/kube-apiserver-master Startup probe failed: HTTP probe failed with statuscode: 500
kube-system 44s Normal Started pod/kube-proxy-h8dtw Started container kube-proxy
kube-system 3m58s Warning Unhealthy pod/kube-scheduler-master Startup probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused
kube-system 44s Normal Killing pod/etcd-master Stopping container etcd
kube-system 3m54s Normal SandboxChanged pod/etcd-master Pod sandbox changed, it will be killed and re-created.
kube-system 3m55s Warning Unhealthy pod/etcd-master Liveness probe failed: Get "http://127.0.0.1:2381/health?exclude=NOSPACE&serializable=true": dial tcp 127.0.0.1:2381: connect: connection refused
kube-system 3m56s Warning Unhealthy pod/kube-controller-manager-master Liveness probe failed: Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refused
kube-system 2m8s Warning BackOff pod/kube-scheduler-master Back-off restarting failed container
kube-system 3m50s Warning BackOff pod/etcd-master Back-off restarting failed container
kube-system 45s Warning BackOff pod/kube-controller-manager-master Back-off restarting failed container
default 3m30s Normal Starting node/master
kube-system 3m20s Normal LeaderElection lease/kube-controller-manager master_b5821a6d-87da-4610-a4f1-44e99558bb5c became leader
kube-system 3m17s Warning FailedScheduling pod/coredns-565d847f94-rwl2h 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
kube-system 3m19s Normal LeaderElection lease/kube-scheduler master_ad99584d-ed40-492d-99c4-972c037831f2 became leader
kube-system 3m17s Warning FailedScheduling pod/coredns-565d847f94-cz525 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
default 3m8s Normal RegisteredNode node/master Node master event: Registered Node master in Controller
kube-system 76s Normal Killing pod/kube-proxy-h8dtw Stopping container kube-proxy
kube-system 74s Normal SandboxChanged pod/kube-proxy-h8dtw Pod sandbox changed, it will be killed and re-created.
kube-system 58s Warning BackOff pod/kube-proxy-h8dtw Back-off restarting failed container
default 2m27s Normal Starting node/master
kube-system 110s Normal LeaderElection lease/kube-scheduler master_b9ce6d92-96a7-4c9e-9b20-bdbd2d7e9ab3 became leader
kube-system 110s Warning FailedScheduling pod/coredns-565d847f94-rwl2h 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
kube-system 110s Warning FailedScheduling pod/coredns-565d847f94-cz525 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
default 14s Normal Starting node/master
journalctl -xeu kubelet
Sep 15 20:59:14 master kubelet[1617206]: I0915 20:59:14.596159 1617206 status_manager.go:667] "Failed to get status for pod" podUID=edc5a688c565c0fc9e19bae02d7bd288 pod="kube-system/kube-scheduler-master" err="Get \"https://192.168.1.7:6443/api/v1/namespaces/kube-system/pods/kube-scheduler-master\": dial tcp 192.168.1.7:6443: connect: connection refused"
Sep 15 20:59:14 master kubelet[1617206]: I0915 20:59:14.596828 1617206 status_manager.go:667] "Failed to get status for pod" podUID=9c00203784e24a81ba39f86728fc5311 pod="kube-system/kube-controller-manager-master" err="Get \"https://192.168.1.7:6443/api/v1/namespaces/kube-system/pods/kube-controller-manager-master\": dial tcp 192.168.1.7:6443: connect: connection refused"
Sep 15 20:59:14 master kubelet[1617206]: I0915 20:59:14.597326 1617206 status_manager.go:667] "Failed to get status for pod" podUID=2eca7554e513baa34e410b69400055e9 pod="kube-system/kube-apiserver-master" err="Get \"https://192.168.1.7:6443/api/v1/namespaces/kube-system/pods/kube-apiserver-master\": dial tcp 192.168.1.7:6443: connect: connection refused"
Sep 15 20:59:14 master kubelet[1617206]: I0915 20:59:14.597879 1617206 status_manager.go:667] "Failed to get status for pod" podUID=806f7e7e-5ed1-4bb9-89ca-0046bb6af05d pod="kube-system/kube-proxy-h8dtw" err="Get \"https://192.168.1.7:6443/api/v1/namespaces/kube-system/pods/kube-proxy-h8dtw\": dial tcp 192.168.1.7:6443: connect: connection refused"
Sep 15 20:59:14 master kubelet[1617206]: I0915 20:59:14.598318 1617206 status_manager.go:667] "Failed to get status for pod" podUID=c93a7381438357ccf8aaac445696c8e0 pod="kube-system/etcd-master" err="Get \"https://192.168.1.7:6443/api/v1/namespaces/kube-system/pods/etcd-master\": dial tcp 192.168.1.7:6443: connect: connection refused"
Sep 15 20:59:15 master kubelet[1617206]: E0915 20:59:15.213086 1617206 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
Sep 15 20:59:16 master kubelet[1617206]: I0915 20:59:16.678305 1617206 scope.go:115] "RemoveContainer" containerID="5afd259003d8b2cf3782ff74c84bf25112e02b4dc0f5067c8aae4fce368c4ec3"
Sep 15 20:59:16 master kubelet[1617206]: E0915 20:59:16.678834 1617206 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-proxy\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=kube-proxy pod=kube-proxy-h8dtw_kube-system(806f7e7e-5ed1-4bb9-89ca-0046bb6af05d)\"" pod="kube-system/kube-proxy-h8dtw" podUID=806f7e7e-5ed1-4bb9-89ca-0046bb6af05d
Sep 15 20:59:19 master kubelet[1617206]: I0915 20:59:19.684682 1617206 scope.go:115] "RemoveContainer" containerID="ee3a9dc76a63033a2b44954eb834d319bc0538013ca4611b6850c2b3badd3783"
Sep 15 20:59:19 master kubelet[1617206]: E0915 20:59:19.685861 1617206 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-apiserver\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=kube-apiserver pod=kube-apiserver-master_kube-system(2eca7554e513baa34e410b69400055e9)\"" pod="kube-system/kube-apiserver-master" podUID=2eca7554e513baa34e410b69400055e9
Sep 15 20:59:20 master kubelet[1617206]: E0915 20:59:20.009427 1617206 controller.go:144] failed to ensure lease exists, will retry in 7s, error: Get "https://192.168.1.7:6443/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/master?timeout=10s": dial tcp 192.168.1.7:6443: connect: connection refused
Sep 15 20:59:20 master kubelet[1617206]: E0915 20:59:20.214897 1617206 kubelet.go:2373] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
Sep 15 20:59:20 master kubelet[1617206]: E0915 20:59:20.522423 1617206 event.go:276] Unable to write event: '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"kube-apiserver-master.17151476f5e14306", GenerateName:"", Namespace:"kube-system", SelfLink:"", UID:"", ResourceVersion:"12859", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Pod", Namespace:"kube-system", Name:"kube-apiserver-master", UID:"2eca7554e513baa34e410b69400055e9", APIVersion:"v1", ResourceVersion:"", FieldPath:"spec.containers{kube-apiserver}"}, Reason:"Unhealthy", Message:"Startup probe failed: HTTP probe failed with statuscode: 500", Source:v1.EventSource{Component:"kubelet", Host:"master"}, FirstTimestamp:time.Date(2022, time.September, 15, 20, 38, 58, 0, time.Local), LastTimestamp:time.Date(2022, time.September, 15, 20, 53, 48, 548094571, time.Local), Count:25, Type:"Warning", EventTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'Patch "https://192.168.1.7:6443/api/v1/namespaces/kube-system/events/kube-apiserver-master.17151476f5e14306": dial tcp 192.168.1.7:6443: connect: connection refused'(may retry after sleeping)
kubectl get nodes
The connection to the server 192.168.1.7:6443 was refused - did you specify the right host or port?