kubectl config use-context staging-cluster kubectl get pods Now you see crashing pods. You check logs. You find the bug. Alex thanks you. You finish your coffee — still warm enough.
kubectl config current-context
kubectl logs auth-service-7d8f9b-xk2lm But the logs show nothing unusual. In fact, they show only low-volume test traffic — not the user load Alex mentioned. That’s weird. kubectl context
kubectl get pods The list that appears shows five pods, all with names like auth-service-7d8f9b-xk2lm . They look healthy. Everything seems fine.
kubectl config use-context staging-cluster — put your current context right in your terminal prompt: Alex thanks you
export PS1="[\u@\h \$(kubectl config current-context)] \$ " Now you’ll see something like [alex@laptop dev-cluster] $ — no more guessing.
Then it hits you. You forgot to check your . In fact, they show only low-volume test traffic
From that day on, your first command every morning is: