A county runbook allows kubectl exec or attach, but the first triage step for a misbehaving app is unclear. What practice best matches non-invasive troubleshooting?
Select an answer to reveal the explanation.
Short Explanation
Peek at the diary before kicking the door in—logs and events are the polite first look. Save exec and attach for when the pages aren’t enough.
Full Explanation
Non-invasive diagnostics—logs, describe, events, and status—should precede interactive exec/attach, which can alter process state or require elevated RBAC. Starting with a shell, silencing stdout, or deleting Pods as a first step skips evidence and can worsen outages.