1

curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"

1

sudo install -o root -g root -m 0755 kubectl /usr/local/bin/kubectl

1

source <(kubectl completion zsh)

1

apt-get install -y apt-transport-https ca-certificates curl gpg

1
2
3

# 如果 `/etc/apt/keyrings` 目录不存在，则应在 curl 命令之前创建它，请阅读下面的注释。
# sudo mkdir -p -m 755 /etc/apt/keyrings
curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.32/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

1
2

# 此操作会覆盖 /etc/apt/sources.list.d/kubernetes.list 中现存的所有配置。
echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.32/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list

1
2
3

sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl
sudo apt-mark hold kubelet kubeadm kubectl

1
2

sudo swapoff -a                     # 临时关闭
sudo sed -i '/ swap / s/^/#/' /etc/fstab  # 永久关闭

1
2
3

sudo kubeadm init \
  --pod-network-cidr=10.244.0.0/16 \  # Calico 网络插件的默认 CIDR
  --apiserver-advertise-address=<MASTER_IP>  # 替换为 Master 节点的公网 IP

1
2
3
4
5
6
7
8

# root @ k8s-master in ~ [17:14:08] C:1
$ sudo kubeadm init \
  --pod-network-cidr=10.244.0.0/16 \  
  --apiserver-advertise-address=114.514.191.981  

unknown command "\u00a0" for "kubeadm init"
To see the stack trace of this error execute with --v=5 or higher
zsh: command not found:  

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

# root @ k8s-master in ~ [17:19:19] C:127
$ sudo kubeadm init \
> --pod-network-cidr=10.244.0.0/16 \
> --apiserver-advertise-address=19.19.81.0
[init] Using Kubernetes version: v1.32.2
[preflight] Running pre-flight checks
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action beforehand using 'kubeadm config images pull'
W0301 17:20:46.188020  457167 checks.go:846] detected that the sandbox image "registry.k8s.io/pause:3.6" of the container runtime is inconsistent with that used by kubeadm.It is recommended to use "registry.k8s.io/pause:3.10" as the CRI sandbox image.
[certs] Using certificateDir folder "/etc/kubernetes/pki"
[certs] Generating "ca" certificate and key
[certs] Generating "apiserver" certificate and key
[certs] apiserver serving cert is signed for DNS names [k8s-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 19.19.81.0]
[certs] Generating "apiserver-kubelet-client" certificate and key
[certs] Generating "front-proxy-ca" certificate and key
[certs] Generating "front-proxy-client" certificate and key
[certs] Generating "etcd/ca" certificate and key
[certs] Generating "etcd/server" certificate and key
[certs] etcd/server serving cert is signed for DNS names [k8s-master localhost] and IPs [19.19.81.0 127.0.0.1 ::1]
[certs] Generating "etcd/peer" certificate and key
[certs] etcd/peer serving cert is signed for DNS names [k8s-master localhost] and IPs [19.19.81.0 127.0.0.1 ::1]
[certs] Generating "etcd/healthcheck-client" certificate and key
[certs] Generating "apiserver-etcd-client" certificate and key
[certs] Generating "sa" key and public key
[kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[kubeconfig] Writing "admin.conf" kubeconfig file
[kubeconfig] Writing "super-admin.conf" kubeconfig file
[kubeconfig] Writing "kubelet.conf" kubeconfig file
[kubeconfig] Writing "controller-manager.conf" kubeconfig file
[kubeconfig] Writing "scheduler.conf" kubeconfig file
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Starting the kubelet
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests"
[kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s
[kubelet-check] The kubelet is healthy after 500.924104ms
[api-check] Waiting for a healthy API server. This can take up to 4m0s

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

Unfortunately, an error has occurred:
        context deadline exceeded

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
        - 'systemctl status kubelet'
        - 'journalctl -xeu kubelet'

Additionally, a control plane component may have crashed or exited when started by the container runtime.
To troubleshoot, list all containers using your preferred container runtimes CLI.
Here is one example how you may list all running Kubernetes containers by using crictl:
        - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock ps -a | grep kube | grep -v pause'
        Once you have found the failing container, you can inspect its logs with:
        - 'crictl --runtime-endpoint unix:///var/run/containerd/containerd.sock logs CONTAINERID'
error execution phase wait-control-plane: could not initialize a Kubernetes cluster
To see the stack trace of this error execute with --v=5 or higher

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16

# root @ k8s-master in ~ [17:25:24] C:1
$ systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
     Active: active (running) since Sat 2025-03-01 17:21:23 CST; 7min ago
       Docs: https://kubernetes.io/docs/
   Main PID: 457406 (kubelet)
      Tasks: 11 (limit: 4490)
     Memory: 35.9M
        CPU: 3.162s
     CGroup: /system.slice/kubelet.service
             └─457406 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/li>
Mar 01 17:28:18 k8s-master kubelet[457406]: I0301 17:28:18.531707  457406 kubelet_node_status.go:76] "Attempting to register node" node="k8s-master"
Mar 01 17:28:22 k8s-master kubelet[457406]: E0301 17:28:22.753930  457406 kubelet.go:3196] "No need to create a mirror pod, since failed to get node info from >Mar 01 17:28:22 k8s-master kubelet[457406]: I0301 17:28:22.753996  457406 scope.go:117] "RemoveContainer" containerID="f20da810cbdb2ccf29cd8e95001c597b5b32d3e3>Mar 01 17:28:22 k8s-master kubelet[457406]: E0301 17:28:22.754118  457406 pod_workers.go:1301] "Error syncing pod, skipping" err="failed to \"StartContainer\" >Mar 01 17:28:23 k8s-master kubelet[457406]: E0301 17:28:23.833994  457406 eviction_manager.go:292] "Eviction manager: failed to get summary stats" err="failed >Mar 01 17:28:24 k8s-master kubelet[457406]: W0301 17:28:24.467354  457406 reflector.go:569] k8s.io/client-go/informers/factory.go:160: failed to list *v1.Node:>Mar 01 17:28:24 k8s-master kubelet[457406]: E0301 17:28:24.467417  457406 reflector.go:166] "Unhandled Error" err="k8s.io/client-go/informers/factory.go:160: F>Mar 01 17:28:25 k8s-master kubelet[457406]: W0301 17:28:25.965697  457406 reflector.go:569] k8s.io/client-go/informers/factory.go:160: failed to list *v1.CSIDr>Mar 01 17:28:25 k8s-master kubelet[457406]: E0301 17:28:25.965764  457406 reflector.go:166] "Unhandled Error" err="k8s.io/client-go/informers/factory.go:160: F>Mar 01 17:28:26 k8s-master kubelet[457406]: E0301 17:28:26.387444  457406 controller.go:145] "Failed to ensure lease exists, will retry" err="Get \"https://43.>lines 1-23/23 (END)

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

# 重置 kubeadm
sudo kubeadm reset

# 重启 containerd 和 kubelet
sudo systemctl restart containerd
sudo systemctl restart kubelet

# 清理 CNI 配置 (如果有)
sudo rm -rf /etc/cni/net.d/*

# 重新初始化
sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=<IP> --v=5

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

# 首先创建目录（如果不存在）
sudo mkdir -p /etc/network/interfaces.d/

# 创建虚拟网卡配置
sudo tee /etc/network/interfaces.d/eth0:1 <<EOF
auto eth0:1
iface eth0:1 inet static
    address 19.19.81.0
    netmask 255.255.255.255
EOF

# 立即应用配置
sudo ifup eth0:1

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

Your Kubernetes control-plane has initialized successfully!

To start using your cluster, you need to run the following as a regular user:

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

Alternatively, if you are the root user, you can run:

  export KUBECONFIG=/etc/kubernetes/admin.conf

You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
  https://kubernetes.io/docs/concepts/cluster-administration/addons/

Then you can join any number of worker nodes by running the following on each as root:

kubeadm join 19.19.81.0:6443 --token qwim1m.ov8fzob0zq41m8xc \
        --discovery-token-ca-cert-hash sha256:14b6902dee789af56faeff6ea78830e7e9fad1192fd7a7bf301a56219e67a24c 

1
2

# 使用 Calico 网络插件
kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

# root @ k8s-hk-node1 in ~ [11:29:36] 
$ sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=114.514.19.19
[init] Using Kubernetes version: v1.32.2
[preflight] Running pre-flight checks
W0302 11:29:51.341165  133953 checks.go:1077] [preflight] WARNING: Couldn't create the interface used for talking to the container runtime: failed to create new CRI runtime service: validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/containerd/containerd.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
        [WARNING Swap]: swap is supported for cgroup v2 only. The kubelet must be properly configured to use swap. Please refer to https://kubernetes.io/docs/concepts/architecture/nodes/#swap-memory, or disable swap on the node
[preflight] Pulling images required for setting up a Kubernetes cluster
[preflight] This might take a minute or two, depending on the speed of your internet connection
[preflight] You can also perform this action beforehand using 'kubeadm config images pull'
error execution phase preflight: [preflight] Some fatal errors occurred:
failed to create new CRI runtime service: validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/containerd/containerd.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

1
2
3
4
5
6

# 创建默认配置
sudo mkdir -p /etc/containerd
sudo containerd config default | sudo tee /etc/containerd/config.toml > /dev/null

# 编辑配置文件
sudo vi /etc/containerd/config.toml

1
2
3
4

# root @ k8s-hk-node1 in ~ [13:41:08] 
$ telnet 19.19.81.0 6443
Trying 19.19.81.0...
telnet: Unable to connect to remote host: Connection refused

1
2
3
4
5
6

# root @ k8s-master in ~ [21:48:04] 
$ tcpdump -i eth0 'tcp port 6443 and host 114.514.19.19'
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
21:48:15.463636 IP 114.514.19.19.42444 > 10.3.0.13.6443: Flags [S], seq 474053441, win 64240, options [mss 1424,sackOK,TS val 2636673266 ecr 0,nop,wscale 7], length 0
21:48:15.463693 IP 10.3.0.13.6443 > 114.514.19.19.42444: Flags [R.], seq 0, ack 474053442, win 0, length 0

1

sed -i 's|192.168.0.0/16|10.244.0.0/16|g' calico.yaml

1
2

wget https://raw.githubusercontent.com/flannel-io/flannel/v0.22.0/Documentation/kube-flannel.yml\n
kubectl apply -f kube-flannel.yml

1

kubectl create deployment nginx --image=nginx

1
2

nerdctl pull nginx:latest
crictl pull nginx:latest

1

kubectl get deployments