 Okay, if we're accessing a container's logs, it's pretty straightforward. So if I come in and do Docker PS, we can see the containers that I have running. So that is the KBE Raspberry, the Spring Boot application that is running for Kubernetes. So if I grab this ID, and if I just do Docker logs like so, you can see that I'm getting the logs for that. And I could, if I was interested in tailing that, I could do minus F, and then it would sit there. And if any new log data came up, I'd get that. However, in a Kubernetes context, I'll clear this. You might be working with a Kubernetes cluster, and you might not be on that node where Docker is running. So remember, when we deploy Kubernetes in a production environment, we're going to be dealing with multiple servers that are going to be running Docker and containers and whatnot. You won't have that be able to just jump into a node like that. Fortunately, for Kubernetes, we can easily see the same log data. So I can do kubectl get all. And this command shows me the pod that I'm interested in. So what I can do here is I'm just copying this pod identifier. And this would work with any pod in the cluster for Kubernetes. So what I can do is, again, kubectl, I can say logs, I can say tail equals 20, and then pass in the name of the pod. And that will provide the log information inside the log. And then also, I could do minus F to follow if I want to follow logs. So you can see here that I'm on the screen. And if there's any new log information that would be initialized here, unfortunately, we don't have anything outputting log data. The container is just up and running and waiting for requests. But if I did have activity that I wanted to monitor, I would be able to do it through this utility. So let me clear that. So again, those commands are kubectl logs minus F to follow. Or you can do minus tail equals 20 or however many last few lines that you want from that. And that is also optional. So you don't need to give that. You can omit that, hit that. And then it's just going to show you the log data. And I'm not, I'm honestly not sure what the default there is. So it is going to show you a screen full log data without that. So pretty handy utility to see the logs of your application running inside the container.