Logs and events

A customer says order 42 came late. The kitchen tray says Running. Where do you look first?

~/shop $ kubectl logs kitchenorder 41 readyorder 42 oven too coldorder 42 ready

Logslogs: The cook's notebook: everything a container prints. are the cook’s notebook: everything the container prints. kubectl logs kitchen reads it. There’s the clue: the oven was too cold.

Busy cooks write long notebooks. Show only the last line with --tail=1.

~/shop $ kubectl get podsNAME                    READY   STATUS             RESTARTS      AGEoops-6c5fb65c57-ht8mq   0/1     CrashLoopBackOff   3 (13s ago)   46s~/shop $ kubectl logs oops-6c5fb65c57-ht8mq --previousstarting the kitchenoh no, no gas

CrashLoopBackOff: the tray keeps crashing, so Kubernetes waits longer between restarts. Each restart starts a clean notebook. --previous reads the notebook from the run that crashed.

You delete the kitchen pod. A new one takes its place. Can you still read the old pod’s logs?

~/shop $ kubectl get events --field-selector involvedObject.name=kitchenLAST SEEN   TYPE     REASON      OBJECT        MESSAGE14s         Normal   Scheduled   pod/kitchen   Successfully assigned default/kitchen to dev-worker13s         Normal   Pulling     pod/kitchen   Pulling image "busybox:1.37"12s         Normal   Pulled      pod/kitchen   Successfully pulled image "busybox:1.37" in 1.868s (1.868s including waiting). Image size: 2150000 bytes.12s         Normal   Created     pod/kitchen   Created container: cook12s         Normal   Started     pod/kitchen   Started container cook

Eventsevent: A note on the manager's notice board: scheduled, pulled, started, or a warning. Kept for a short time. are the manager’s notice board: placed, pulled, started, and warnings. Kubernetes writes them, not your app. They fade after a short time.

Notebook or notice board? Sort each line.

You can now read a tray’s logs and the zone’s events.