How to View Logs Using Kubectl in 2025?

In the ever-evolving world of Kubernetes, efficiently managing and troubleshooting applications requires a solid understanding of how to access and interpret logs. As of 2025, viewing logs using kubectl continues to be a fundamental skill for DevOps professionals. Here’s a simple, step-by-step guide to viewing logs using kubectl.

Prerequisites

Before you begin, ensure you have kubectl installed and configured. If you need to set up kubectl on Windows, follow this guide to install kubectl in PowerShell.

Steps to View Logs

1. Identify Your Pod

First, you need to identify the pod from which you want to view logs. You can list all pods in a specific namespace using:

1

   kubectl get pods -n <namespace>

Make sure to replace <namespace> with your actual namespace.

1. View Logs for a Single Container Pod

For a pod with a single container, retrieve the logs using:

1

   kubectl logs <pod-name> -n <namespace>

This command fetches all the logs from the specified pod.

1. View Logs for Multi-Container Pods

For pods with multiple containers, specify the container name:

1

   kubectl logs <pod-name> -c <container-name> -n <namespace>

1. Stream Logs Continuously

To stream logs in real-time, append the -f flag, which allows you to follow the logs:

1

   kubectl logs -f <pod-name> -n <namespace>

1. View Logs for Previous Instance

If you need logs from a previous instance of a pod, use the --previous flag:

1

   kubectl logs <pod-name> --previous -n <namespace>

Conclusion

Mastering log retrieval using kubectl is crucial for diagnosing issues and ensuring smooth application operations in Kubernetes environments. With these commands, you can effectively monitor your applications and maintain a high level of operational excellence.

For further reading and resources on using kubectl, including setup on various operating systems, refer to our PowerShell kubectl setup guide.

By keeping your skills updated with the latest practices, you’ll be well-prepared to tackle Kubernetes challenges in 2025 and beyond!