Kubernetes Scenario Labs
Repair pods, services, deployments, RBAC, and network policies
How It Works
Each lab drops you into a broken config. Your job: find the bug and fix it.
Read the Scenario
Understand what went wrong — a teammate pushed broken config and CI is failing.
Debug in the Terminal
Run the tool, read the errors, and trace them back to the source.
Fix & Verify
Edit the config, re-run the check, and confirm a clean result.
Beginner
4 labsStart here — core concepts and simple fixes
Fix ConfigMap Volume Mount
Fix mismatched volume names and ConfigMap references in a Pod spec.
Fix Deployment Selector
Fix mismatched selector.matchLabels and template labels in a Deployment.
Fix Ingress Rules
Fix wrong service references, ports, and missing ingress class in an Ingress resource.
Fix Liveness & Readiness Probes
Fix broken health check probes causing pods to restart in a loop.
Intermediate
3 labsLevel up — multi-resource configs and debugging
Fix Network Policy
Fix a NetworkPolicy that blocks all traffic due to wrong selectors and port rules.
Fix Pod Image and Port
Fix a typo in the container image name and a port mismatch in a Pod manifest.
Fix PersistentVolumeClaim
Fix a PVC with wrong StorageClass, access mode, and mount path for a StatefulSet.
Advanced
3 labsExpert mode — complex configurations and edge cases
Fix RBAC Permissions
Fix broken Role apiGroups, resource names, and RoleBinding references.
Fix Resource Limits
Fix invalid resource requests/limits causing OOMKilled pods in a Deployment.
Fix Service Configuration
Fix a Service with wrong selectors and port mappings that can't route to pods.