BM: Baca dalam Bahasa Melayu
World K9: Cluster Admin
crictl: containers under the kubelet
You will learn: how to see a node’s pods, containers and logs straight from the stove.
Checked with Kubernetes 1.37 on 1 Nov 2026
The problem
kind-dev namespace defaultThe oven tray keeps crashing on dev-worker2. On a bad night, the office is down too. Then kubectl sees nothing. How do you look anyway?
Try it
Go straight to the stove with crictl: A torch to look straight at the stove: it lists the pods and containers containerd runs on one node.. Type docker exec -it dev-worker2 bash, then crictl pods.
kind-dev namespace defaultdev-control-planeOpenManagerNo trays here.
dev-workerOpenNo trays here.
dev-worker2Open- oven↻2CrashLoopBackOff
Hint
crictl talks to containerd on this one machine. It needs no API server.Try it
crictl ps -a lists containers, stopped ones too. Tap the container that exited.
Tap the container that exited.
0 of 1 found
Hint
Read the STATE column.Try it
Read the oven’s last words. Type crictl ps -a --name oven. Copy the CONTAINER id. Then type crictl logs and paste it.
kind-dev namespace defaultdev-control-planeOpenManagerNo trays here.
dev-workerOpenNo trays here.
dev-worker2Open- oven↻2CrashLoopBackOff
You are inside node dev-worker2. Type exit to go back to your laptop.
Hint
The first few letters of the id are enough.Predict
The API server is down. Which command still shows the oven’s last words?
Pick one answer.
Check
Which tool fits? Sort each job.
Drag a card into a box. Or tap the card, then tap the box.
Hint
Does the job need the whole food court, or just this machine?Check
Put the steps in order: why does a tray crash?
First step at the top. Put these in order. Use the arrows, or drag.
- Step inside: ssh dev-worker2
- Find its stall: kubectl get pods -o wide
- Find the container: crictl ps -a --name oven
- Read its last words: crictl logs <id>
- Leave the stall: exit
You did it!
You can now see a node’s containers and logs with crictl.
Go deeper (optional)
Use crictl to look. The kubelet runs the containers, so let the kubelet make the changes. crictl images lists what the stove has pulled. crictl inspect <id> shows one container in full.
Real mission
kubectl config current-contextdocker exec dev-worker crictl podsdocker exec dev-worker crictl ps -adocker exec dev-worker crictl images
0 of 4 steps done · Your ticks are saved.
Bahasa Melayu
Dulang oven asyik ranap di dev-worker2. Pada malam yang malang, pejabat pun mati. Jadi kubectl tak nampak apa-apa. Macam mana nak tengok juga?
Pergi terus ke dapur dengan crictl. Taip docker exec -it dev-worker2 bash, kemudian crictl pods.
crictl ps -a senaraikan container, termasuk yang sudah berhenti. Tekan container yang sudah keluar.
Baca kata-kata terakhir oven. Taip crictl ps -a --name oven. Salin id CONTAINER. Kemudian taip crictl logs dan tampal id itu.
API server mati. Arahan mana masih tunjuk kata-kata terakhir oven?
Alat mana yang sesuai? Susun setiap kerja.
Susun langkahnya: kenapa dulang ranap?
Kini anda boleh lihat container dan log sesebuah node dengan crictl.
You finished this before. Practice is always welcome!
Official docs: Debugging Kubernetes nodes with crictl · Container Runtime Interface (CRI) · Debug running pods
You've learned for 25 minutes. A short break helps your brain.
Sprint done! Great focus. Stretch for a minute?