Cloud-Origins/kcna-killercoda-scenarios

34 compressed (<1hr) hands-on Killercoda scenarios for KCNA exam prep, built for the Kubernetes African Developer Training Program 2026 (Andela x CNCF) # KCNA Killercoda Scenarios Compressed, hands-on Kubernetes and Cloud Native Associate (KCNA) exam-prep scenarios in Killercoda's native format. Built for the **Kubernetes African Developer Training Program 2026** (Andela x CNCF). 34 scenarios, each deployable and completable in under one hour, covering all five KCNA exam domains: Cloud Native Architecture, Container Orchestration, Kubernetes Fundamentals, Cloud Native Observability, and Cloud Native Application Delivery. ## Overview Levels 1-21 are adapted from `Cloud-Origins/africa-k8s-labs`, a 19-lab KCNA track averaging roughly 34 hours to complete. Each lab was compressed to under an hour without cutting rigor -- scope was narrowed per scenario, not rushed. Levels 22-34 are self-authored additions that close domain gaps identified against a fuller topic breakdown of the exam (container runtimes, autoscaling, serverless, CI/CD, logging, tracing, and a closing mock exam). They follow the identical file structure, compression discipline, and verification standard as 1-21. Every scenario ships with a real, scripted `verify.sh` per step -- nothing is graded on trust. Checks read live cluster state (pod phases, endpoint IPs, HTTP responses, API query results), not object existence alone. ## Prerequisites - A Killercoda account to run scenarios as-is, **or** a self-hosted Educates instance with minor manifest translation - Familiarity with `kubectl` -- these are exam-prep scenarios, not a Kubernetes introduction - No local tooling required to *run* a scenario; Killercoda provisions the cluster ## Quick Start Fork this repository, then point Killercoda's scenario importer at any scenario folder: ```bash git clone github.com cd kcna-killercoda-scenarios # Each folder under scenarios/ is a complete, independent Killercoda scenario ls scenarios/ ``` In Killercoda, create a new scenario from a Git repository and set the scenario path to `scenarios/01-nodes-cl …