Dunia K9: Pentadbir Kluster

Kubelet: systemctl dan journalctl

Anda akan belajar: cara semak, mulakan semula dan baca kubelet dari dalam node.

Teks BM belum disemak oleh penutur asli.

Disemak dengan Kubernetes 1.37 pada 1 Nov 2026

Masalahnya

Satu mesin but semula pukul 3 pagi. Tak lama kemudian gerainya Ready semula. Tiada siapa taip apa-apa. Siapa hidupkan penyelianya, kubelet?

Tengok

Anda di sini: kluster kind-dev namespace default

~/shop $ ssh dev-worker# kind nodes have no SSH server: on kind you type docker exec -it dev-worker bash. Here ssh opens the same node shell, like on the exam.root@dev-worker:~# systemctl status kubelet● kubelet.service - kubelet: The Kubernetes Node Agent     Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; preset: enabled)    Drop-In: /etc/systemd/system/kubelet.service.d             └─10-kubeadm.conf, 11-kind.conf     Active: active (running) since Sat 2026-10-31 00:55:03 UTC; 5min ago Invocation: 2191aa2042fa6701372c44f6e47756bf       Docs: http://kubernetes.io/docs/    Process: 331 ExecStartPre=/bin/sh -euc if [ -f /sys/fs/cgroup/cgroup.controllers ]; then /kind/bin/create-kubelet-cgroup-v2.sh; fi (code=exited, status=0/SUCCESS)    Process: 340 ExecStartPre=/bin/sh -euc if [ ! -f /sys/fs/cgroup/cgroup.controllers ] && [ ! -d /sys/fs/cgroup/systemd/kubelet ]; then mkdir -p /sys/fs/cgroup/systemd/kubelet; fi (code=exited, status=0/SUCCESS)   Main PID: 342 (kubelet)      Tasks: 11 (limit: 1263)     Memory: 26.6M (peak: 27.1M)        CPU: 854ms     CGroup: /kubelet.slice/kubelet.service             └─342 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.3 --provider-id=kind://docker/dev/dev-worker --node-labels= --runtime-cgroups=/system.slice/containerd.serviceOct 31 00:55:03 dev-worker systemd[1]: Started kubelet.service - kubelet: The Kubernetes Node Agent.Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.023576     342 server.go:545] "Kubelet version" kubeletVersion="v1.37.0"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.025588     342 server.go:547] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.028500     342 kubelet.go:389] "Adding static pod path" path="/etc/kubernetes/manifests"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.031412     342 kubelet.go:400] "Adding apiserver pod source"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.034324     342 kuberuntime_manager.go:315] "Container runtime initialized" containerRuntime="containerd" version="v2.3.4" apiVersion="v1"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.037236     342 server.go:1336] "Started kubelet"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.039952     342 server.go:196] "Starting to listen" address="0.0.0.0" port=10250Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.041964     342 volume_manager.go:331] "Starting Kubelet Volume Manager"Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.045523     342 reconciler.go:29] "Reconciler: start to sync state"

Di dalam dev-worker: systemctl status kubelet kata loaded dan enabled, active (running), dengan baris journal terakhir kubelet di bawahnya. Output terminal: $ ssh dev-worker # kind nodes have no SSH server: on kind you type docker exec -it dev-worker bash. Here ssh opens the same node shell, like on the exam. $ systemctl status kubelet ● kubelet.service - kubelet: The Kubernetes Node Agent Loaded: loaded (/etc/systemd/system/kubelet.service; enabled; preset: enabled) Drop-In: /etc/systemd/system/kubelet.service.d └─10-kubeadm.conf, 11-kind.conf Active: active (running) since Sat 2026-10-31 00:55:03 UTC; 5min ago Invocation: 2191aa2042fa6701372c44f6e47756bf Docs: http://kubernetes.io/docs/ Process: 331 ExecStartPre=/bin/sh -euc if [ -f /sys/fs/cgroup/cgroup.controllers ]; then /kind/bin/create-kubelet-cgroup-v2.sh; fi (code=exited, status=0/SUCCESS) Process: 340 ExecStartPre=/bin/sh -euc if [ ! -f /sys/fs/cgroup/cgroup.controllers ] && [ ! -d /sys/fs/cgroup/systemd/kubelet ]; then mkdir -p /sys/fs/cgroup/systemd/kubelet; fi (code=exited, status=0/SUCCESS) Main PID: 342 (kubelet) Tasks: 11 (limit: 1263) Memory: 26.6M (peak: 27.1M) CPU: 854ms CGroup: /kubelet.slice/kubelet.service └─342 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --node-ip=172.18.0.3 --provider-id=kind://docker/dev/dev-worker --node-labels= --runtime-cgroups=/system.slice/containerd.service Oct 31 00:55:03 dev-worker systemd[1]: Started kubelet.service - kubelet: The Kubernetes Node Agent. Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.023576 342 server.go:545] "Kubelet version" kubeletVersion="v1.37.0" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.025588 342 server.go:547] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK="" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.028500 342 kubelet.go:389] "Adding static pod path" path="/etc/kubernetes/manifests" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.031412 342 kubelet.go:400] "Adding apiserver pod source" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.034324 342 kuberuntime_manager.go:315] "Container runtime initialized" containerRuntime="containerd" version="v2.3.4" apiVersion="v1" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.037236 342 server.go:1336] "Started kubelet" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.039952 342 server.go:196] "Starting to listen" address="0.0.0.0" port=10250 Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.041964 342 volume_manager.go:331] "Starting Kubelet Volume Manager" Oct 31 00:55:03 dev-worker kubelet[342]: I1031 00:55:03.045523 342 reconciler.go:29] "Reconciler: start to sync state"

Pengurus servis itu ialah , bilik kuasa mesin. systemctl status kubelet tanya ia: penyelia sedang bertugas, dan sejak bila?

Cuba

Baca macam pentadbir. Tekan dua baris: “hidup semasa but” dan “berjalan sekarang”.

Tekan 2 baris yang paling penting.

0 daripada 2 dijumpai

Cuba

Selepas tetapan kubelet berubah, anda mulakan semula. Taip ssh dev-worker, kemudian systemctl restart kubelet. Kemudian baca : journalctl -u kubelet -n 5 --no-pager. Hati-hati: restart mengubah node.

Anda di sini: kluster kind-dev namespace default

dev-control-planeBukaPengurus

Tiada dulang di sini.

dev-workerBuka

shop·7fm98
shop·l72qr

dev-worker2Buka

shop·h9k94

Masa: +0s (dipercepat)

Cuba

Bina arahan untuk 20 baris terakhir diari kubelet.

Ketik kepingan ikut turutan yang betul.

…

Teka

Anda hentikan kubelet di dev-worker. Apa jadi pada dulangnya serta-merta?

Semak

Arahan ini cuma melihat, atau mengubah gerai? Susun.

Seret kad ke dalam kotak. Atau ketik kad, kemudian ketik kotak.

Anda berjaya!

Kini anda boleh semak, mulakan semula dan baca kubelet.

Nak tahu lebih (pilihan)

cat /etc/systemd/system/kubelet.service tunjuk Restart=always: jika kubelet ranap, systemd hidupkannya semula. systemctl stop yang dirancang kekal berhenti. journalctl -u kubelet -f ikut baris baharu secara langsung; tekan Ctrl+C untuk keluar.

Misi sebenar

Guna kluster kind pakai buang anda sahaja.
kubectl config current-context
Tanya systemd tentang penyelia satu gerai.
docker exec dev-worker systemctl status kubelet --no-pager
Baca 20 baris terakhir diarinya.
docker exec dev-worker journalctl -u kubelet -n 20 --no-pager
Baca fail servis dan drop-in-nya.
docker exec dev-worker systemctl cat kubelet

0 daripada 4 langkah siap · Tanda anda disimpan.