Got it, let's tackle this problem—you want to skip straight to the end of your pod's logs or focus on the latest entries without scrolling through all historical logs, even after trying the -f flag. Here are several practical, go-to solutions:

• Use --tail to target the latest N lines (with or without follow)
  This is the most straightforward Kubernetes-native way. The --tail flag lets you specify how many of the most recent log lines you want to view immediately. Combine it with -f to keep tracking new logs as they come in:

  # View the last 100 logs and keep following new entries
  kubectl logs <your-pod-name> -c <your-container-name> --tail=100 -f
  
  # Or just view the last 50 logs one-time, no follow
  kubectl logs <your-pod-name> -c <your-container-name> --tail=50
  

  No more scrolling through hundreds of old lines—you start right at the recent stuff.

• Pipe to tail for familiar Linux command workflow
  If you're comfortable with standard Unix tools, pipe the kubectl output to tail to get the same result:

  # Follow logs and only show the latest 100 lines (updates as new logs come)
  kubectl logs <your-pod-name> -c <your-container-name> -f | tail -n 100
  
  # One-time view of the last 30 logs
  kubectl logs <your-pod-name> -c <your-container-name> | tail -n 30
  

• Filter logs by time with --since
  If you don't care about a specific number of lines but want logs from the recent past, use the --since flag to define a time window. This is great if you know an issue started within a certain timeframe:

  # View logs from the last 15 minutes and follow new ones
  kubectl logs <your-pod-name> -c <your-container-name> --since=15m -f
  
  # Or use a specific timestamp (RFC3339 format)
  kubectl logs <your-pod-name> -c <your-container-name> --since="2024-05-20T14:30:00"
  

• Terminal shortcuts to jump to end mid-follow
  If you already ran kubectl logs -f ... and realize you need to jump to the latest logs immediately, most terminal pagers support these shortcuts:

  • Press Shift + G (Vim-style, works in most default terminal setups) to jump straight to the end of the log stream.
  • If your output is being handled by less, just press G to jump to the end, and Ctrl + C to stop following when you're done.

Bonus tip: If your pod has restarted and you need to view logs from the previous container instance, add the --previous flag to any of the above commands (e.g., kubectl logs <pod-name> -c <container-name> --tail=50 --previous).

内容的提问来源于stack exchange，提问作者Vikas Rathore