<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/troubleshooting/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Wed, 21 Oct 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>Troubleshooting an application from A to Z</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/troubleshooting/index.html</link><pubDate>Wed, 21 Oct 2026 08:00:00 +0200</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/troubleshooting/index.html</guid><description>Objective An application has been deployed, and it does not answer. It hides one fault per layer: each fault only shows up once the previous one is fixed, as in real life. In this lab you will:
Follow a method, from the pod scheduling up to the Service Read the pod status, the events and the logs, including the logs of a crashed container Check the Service from inside the cluster On OpenShift, diagnose a crash caused by the SCC, and reproduce it with oc debug Complete this lab in 60 minutes.</description></item></channel></rss>