Buenos Aires: Kubernetes Pod Crashing

Scenario There are two pods: “logger” and “logshipper” living in the default namespace. Unfortunately, logshipper has an issue (crashlooping) and is forbidden to see what logger is trying to say. Could you help fix Logshipper? Because k8s takes a minute or two to change the pod state initially, the check for the scenario is made to fail in the first two minutes. For testing. I need to make sure the following command returns true.