- Lab
-
Libraries: If you want this lab, consider one of these libraries.
- Cloud
Troubleshoot an AKS Workload Rollout
In this Azure lab, you recover a failed application rollout on Azure Kubernetes Service without changing the application's code. You deploy a sample web workload to a pre-provisioned AKS cluster, and the rollout never reaches a healthy, serving state. Working entirely in the Azure portal, you use deployment status, pod events, container logs, and service endpoint details to isolate why the rollout is failing, then remediate an image problem, two runtime problems, and a service problem in turn, validating after each fix that the workload moves closer to steady state. By the end, the deployment is running, its pods are ready, the service has healthy endpoints, and the application path responds. The work mirrors a realistic on-call task: a rollout is failing, and you read the operational signals and apply the smallest correct fix to bring it back.
Lab Info
Table of Contents
-
Challenge
Diagnose and restore the workload's image pull
- Inspect the deployment and pod status to confirm the pods are not reaching a running state.
- Examine the pod events to identify an image pull failure as the cause.
- Correct the workload's image reference so the container image can be pulled.
- Confirm the pods progress past the image pull stage.
-
Challenge
Diagnose and fix the failed container start
- Inspect the pod status and restart behavior to confirm the container is not staying up.
- Examine the pod status and read its (empty) logs to isolate a container start failure that is not an image problem and not an application problem.
- Correct the workload's runtime configuration so the container starts successfully.
- Confirm that the container starts and that the application process begins running.
-
Challenge
Diagnose and correct the misconfigured environment value
- Inspect the pod status to confirm the container now starts, but the application is still crashing.
- Read the application's runtime logs to isolate a startup failure caused by a bad environment value.
- Correct the environment value in the workload configuration.
- Confirm the application starts cleanly and the pods become ready.
-
Challenge
Restore the service endpoints and validate the rollout
- Confirm the pods are now running and ready, but the application path is still unreachable.
- Inspect the service and its endpoints to isolate a selector that does not match the pod labels.
- Correct the service selector so the service routes to the workload's pods.
- Validate that the deployment has reached steady state, the service shows healthy endpoints, and the intended application path responds.
Real skill practice before real-world application
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.
Learn by doing
Engage hands-on with the tools and technologies you’re learning. You pick the skill, we provide the credentials and environment.
Follow your guide
All labs have detailed instructions and objectives, guiding you through the learning process and ensuring you understand every step.
Turn time into mastery
On average, you retain 75% more of your learning if you take time to practice. Hands-on labs set you up for success to make those skills stick.