An image resizer that keeps running out of memory
A batch pod has restarted dozens of times. Read its events and logs with kubectl and find out why an image resizer wants 2 GB of RAM and a mining pool.
Briefing
The data team’s batch namespace is noisy today: one pod has been in CrashLoopBackOff all night, and the node it lands on keeps hitting 100% CPU.
kubectl get pods shows restarts and status, kubectl get events explains them, and kubectl logs shows what the container printed before it died.
ops-bastion · Kubernetes review
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.