get teh logs of the previous (crashed) container, not the current one:
kubectl logs <pod> --previous
kubectl describe pod <pod>
In describe, look at Last State: the Reason and Exit Code tell you a lot. OOMKilled / 137 is memory, Error / 1 is the app exiting, Completed / 0 means the process just finished. fingers crossed 馃
ugh. small config change, rolled out to k3s, and now the worker pod is looping:
rollback would be easy but i want to understand what happened. restart counter keeps climbing and my on-call phone is buzzing.
The change was just a couple of environment variables and a new image tag. Nothing that should break startup, i thought. Whats the fastest way to see why it actually dies bfeore i give up and roll back?
ok so Last State: Terminated, Reason: Error, Exit Code: 1. and --previous finally shows a stack trace about a missing env var. idk what else to say tbh
get teh logs of the previous (crashed) container, not the current one:
kubectl logs <pod> --previous
kubectl describe pod <pod>
In describe, look at Last State: the Reason and Exit Code tell you a lot. OOMKilled / 137 is memory, Error / 1 is the app exiting, Completed / 0 means the process just finished. fingers crossed 馃
Sign in or create an account to reply.