root@pi-102:~# systemctl status k3s-agent
● k3s-agent.service - Lightweight Kubernetes
Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-04-23 17:00:30 CST; 58s ago
Docs: https://k3s.io
Process: 1004 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
Process: 1007 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 1008 (k3s-agent)
Tasks: 31
Memory: 184.7M
CGroup: /system.slice/k3s-agent.service
├─1008 /usr/local/bin/k3s agent
└─1029 containerd
Apr 23 17:01:19 pi-102 k3s[1008]: I0423 17:01:19.221111 1008 shared_informer.go:240] Waiting for caches to sync for endpoint slice config
Apr 23 17:01:19 pi-102 k3s[1008]: I0423 17:01:19.321267 1008 shared_informer.go:247] Caches are synced for service config
Apr 23 17:01:19 pi-102 k3s[1008]: I0423 17:01:19.321412 1008 shared_informer.go:247] Caches are synced for endpoint slice config
在 k3s server 中测试
root@192-168-1-100:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192-168-1-100 Ready control-plane,master 7h26m v1.20.6+k3s1
raspberrypi-101 Ready worker 7h22m v1.20.6+k3s1
pi-102 Ready <none> 30s v1.20.6+k3s1
修改节点 pi-102 角色
root@192-168-1-100:~# kubectl label node pi-102 node-role.kubernetes.io/worker=worker
node/pi-102 labeled
root@192-168-1-100:~# kubectl get nodes
NAME STATUS ROLES AGE VERSION
192-168-1-100 Ready control-plane,master 7h27m v1.20.6+k3s1
raspberrypi-101 Ready worker 7h23m v1.20.6+k3s1
pi-102 Ready worker 98s v1.20.6+k3s1