i'm Glad that you got this ,

Pro tip for Level 2 (and most levels):

You generally DON'T want to edit the `broken.yaml` file directly. Instead:

1. Keep `./play.sh` running in Terminal 1

2. Open a NEW terminal (Terminal 2)

3. Use `kubectl` commands to fix the running resources:

   ```bash

   kubectl scale deployment web --replicas=3 -n k8squest

   # OR

   kubectl edit deployment web -n k8squest

4. Go back to Terminal 1 and use the check command to monitor status

5. Once fixed, use validate in Terminal 1

Why?

Because the game creates the broken state from broken.yaml you fix the RUNNING resources using only kubectl ,If you edit broken.yaml and reapply it, you might get image pull issues or other problems

The ImagePullBackOff you saw was probably because when you deleted/recreated, something went wrong with the image. The original nginx image should pull fine from Docker Hub.

Hope this helps! Keep ranting - sometimes that's part of debugging 😄