Scenario: "Buenos Aires": Kubernetes Pod Crashing

Level: Medium

Type: Fix

Tags: kubernetes   python  

Access: Email

Description: 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?

Do not change the K8S definition of the logshipper pod.

NOTE: Wait about 30 seconds after the pod is stably Ready before using "Check My Solution".

Idea credit: Srivatsav Kondragunta

Root (sudo) Access: True

Test: kubectl get pods -l app=logshipper --no-headers -o json | jq -r '.items[] | "\(.status.containerStatuses[0].ready)"' returns true and stays that way.

The logshipper pod specification has not been changed.

The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute.

Time to Solve: 20 minutes.