During a live transit incident, operators want new log lines as they appear and only the most recent backlog. Which kubectl logs options best match that need?
Select an answer to reveal the explanation.
Short Explanation
Incidents need a live feed—follow sticks with the stream, and tail keeps the backlog short so you're not drowning in yesterday's noise.
Full Explanation
kubectl logs -f follows the stream in real time, and --tail limits how many historical lines are shown first—useful during active incidents. --previous targets an old instance, kubectl cp is not a log tailer, and scaling to zero removes rather than streams diagnostic output.