kubeasy-dev · pbrissaud · Mar 12, 2026 · Mar 12, 2026
diff --git a/access-pending/challenge.yaml b/access-pending/challenge.yaml
@@ -6,6 +6,7 @@ theme: rbac-security
 difficulty: hard
 type: fix
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A new application was deployed that needs to query the Kubernetes API during startup.
   The pod status shows Running, but the Ready condition stays False.

diff --git a/env-config/challenge.yaml b/env-config/challenge.yaml
@@ -6,6 +6,7 @@ theme: volumes-secrets
 difficulty: easy
 type: build
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A web application has been deployed to the namespace.
   When you check the logs, you see: "ERROR: APP_NAME and APP_ENV not configured".

diff --git a/expose-internally/challenge.yaml b/expose-internally/challenge.yaml
@@ -6,6 +6,7 @@ theme: pods-containers
 difficulty: easy
 type: build
 estimatedTime: 10
+minRequiredVersion: 2.0.0
 initialSituation: |
   A web application is deployed and running in the namespace.
   The pods are healthy and serving traffic on port 8080.

diff --git a/first-deployment/challenge.yaml b/first-deployment/challenge.yaml
@@ -6,6 +6,7 @@ theme: pods-containers
 difficulty: easy
 type: build
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   You've been given access to a Kubernetes namespace called "first-deployment".
   The namespace is empty - no resources have been created yet.

diff --git a/first-job/challenge.yaml b/first-job/challenge.yaml
@@ -6,6 +6,7 @@ theme: jobs-cronjobs
 difficulty: easy
 type: build
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   The team needs to run a one-time database migration script.
   The script takes about 30 seconds to complete and outputs "Migration complete!" when done.

diff --git a/grant-access/challenge.yaml b/grant-access/challenge.yaml
@@ -6,6 +6,7 @@ theme: rbac-security
 difficulty: medium
 type: build
 estimatedTime: 20
+minRequiredVersion: 2.0.0
 initialSituation: |
   A monitoring application needs to list pods in its namespace.
   The app uses a dedicated ServiceAccount, but it has no permissions.

diff --git a/job-failed/challenge.yaml b/job-failed/challenge.yaml
@@ -6,6 +6,7 @@ theme: jobs-cronjobs
 difficulty: medium
 type: fix
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A CronJob that processes data every night has been consistently failing.
   Looking at the Job status, you see it has failed multiple times.

diff --git a/missing-credentials/challenge.yaml b/missing-credentials/challenge.yaml
@@ -6,6 +6,7 @@ theme: volumes-secrets
 difficulty: medium
 type: fix
 estimatedTime: 20
+minRequiredVersion: 2.0.0
 initialSituation: |
   A new microservice was deployed that needs to connect to a PostgreSQL database.
   The database credentials are stored in a Kubernetes Secret called "database-credentials".

diff --git a/partial-outage/challenge.yaml b/partial-outage/challenge.yaml
@@ -5,6 +5,7 @@ theme: networking
 difficulty: easy
 type: fix
 estimatedTime: 10
+minRequiredVersion: 2.0.0
 initialSituation: |
   A frontend Deployment with 2 replicas and a backend Deployment with 1 replica are deployed in the same namespace.
   A NetworkPolicy is defined, but users still report issues — possibly related to intra-cluster communication.

diff --git a/persistent-data/challenge.yaml b/persistent-data/challenge.yaml
@@ -6,6 +6,7 @@ theme: volumes-secrets
 difficulty: medium
 type: build
 estimatedTime: 20
+minRequiredVersion: 2.0.0
 initialSituation: |
   A note-taking application is deployed but loses all notes when the pod restarts.
   The application stores notes in /data/notes.txt.

diff --git a/pod-evicted/challenge.yaml b/pod-evicted/challenge.yaml
@@ -6,6 +6,7 @@ theme: resources-scaling
 difficulty: easy
 type: fix
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A data processing application is deployed as a single pod.
   The pod starts but keeps crashing after a few seconds.

diff --git a/privilege-denied/challenge.yaml b/privilege-denied/challenge.yaml
@@ -6,6 +6,7 @@ theme: rbac-security
 difficulty: medium
 type: fix
 estimatedTime: 20
+minRequiredVersion: 2.0.0
 initialSituation: |
   A legacy application was deployed and worked fine for months.
   After a recent cluster update, the pod fails to start.

diff --git a/probes-drift/challenge.yaml b/probes-drift/challenge.yaml
@@ -4,6 +4,7 @@ theme: monitoring-debugging
 difficulty: medium
 type: fix
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A notification service was deployed with health checks configured.
   The container starts, begins initialization, but Kubernetes keeps restarting it in a loop.

diff --git a/stuck-pending/challenge.yaml b/stuck-pending/challenge.yaml
@@ -6,6 +6,7 @@ theme: scheduling-affinity
 difficulty: medium
 type: fix
 estimatedTime: 15
+minRequiredVersion: 2.0.0
 initialSituation: |
   A new application was deployed but the pod stays in Pending state.
   Running kubectl describe pod shows events about node selection.

diff --git a/tainted-out/challenge.yaml b/tainted-out/challenge.yaml
@@ -6,6 +6,7 @@ theme: scheduling-affinity
 difficulty: medium
 type: fix
 estimatedTime: 20
+minRequiredVersion: 2.0.0
 initialSituation: |
   A critical application pod stays Pending indefinitely.
   Running kubectl describe pod shows taint-related errors.

diff --git a/wrong-selector/challenge.yaml b/wrong-selector/challenge.yaml
@@ -6,6 +6,7 @@ theme: pods-containers
 difficulty: easy
 type: fix
 estimatedTime: 10
+minRequiredVersion: 2.0.0
 initialSituation: |
   A web application was deployed with a Deployment and Service.
   The pods are Running and healthy when checked directly.