- Lab
- Cloud
Determining the Reason for Pod Failure
You are a container engineer at Cube4Lyf, an e-gaming platform geared towards puzzle and logic games. One of the pods running a newly launched game is failing. You need to identify the error causing the pod to fail and to extract the error for the logging agent to pick up so the developers, who don't have access to this environment, can view the error and create a patch.
Path Info
Table of Contents
-
Challenge
Investigate the failed pod
The pod
puzzle-plazais in a nonworking state. Using your Kubernetes troubleshooting tools, idenitify the error message. -
Challenge
Filter and write the error message to a file.
The devs behing
puzzle-plazadon't have access to this environment, but need to see the error message. Extract only the error message and write it to anerror.logfile at the root directory of the lab vm.hint: the go template for this is
kubectl get pod puzzle-plaza -o go-template="{{range .status.containerStatuses}}{{.lastState.terminated.message}}{{end}}"
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.
Provided environment for hands-on practice
We will provide the credentials and environment necessary for you to practice right within your browser.
Guided walkthrough
Follow along with the author’s guided walkthrough and build something new in your provided environment!
Did you know?
On average, you retain 75% more of your learning if you get time for practice.