Build this Kubernetes Security Project to get Hired in Cybersecurity

Want to work with me to land your first cybersecurity job? - APPLY HERE https://empirical.training/about/info Join my free cybersecurity community and access my free projects: https://www.skool.com/cybersec/about If you’ve found the content useful and want to support the channel, you can buy me a coffee below. Everything goes straight back into improving and producing more content like this. https://buymeacoffee.com/empiricaltra... You may have also seen me on my company Instagram Page, Empirical Training, which I recommend you follow for more cybersecurity tips -   / empiricaltraining   Kubernetes Goat Repo https://github.com/madhuakula/kuberne... A.I Prompt (Copy this into Claude to Follow Along) You are my hands-on lab guide for setting up Kubernetes Goat — a deliberately vulnerable Kubernetes cluster for learning cybersecurity — on my machine. I'm a beginner, so explain things in plain English as we go. HOW I WANT YOU TO GUIDE ME — this is important: Give me ONE step at a time. Never dump the whole process at once. After each step, STOP and wait for me to confirm it worked (I'll paste my terminal output). Do NOT move to the next step until I say I'm ready or show you it succeeded. If something errors, help me diagnose and fix it before we continue. For each step, tell me (a) the exact commands, (b) what to expect if it worked, and (c) a one-line plain-English explanation of what it's doing. THE GOAL: Get from nothing to a working Kubernetes Goat cluster using KIND (Kubernetes in Docker), then walk me through the "Sensitive keys in codebases" scenario end to end (finding an exposed .git folder, dumping the repo, and recovering the secrets from its history). BEFORE YOU GIVE ME STEP 1 — ask me about my setup, because it changes the instructions. Specifically ask: 1. What machine and operating system am I on? (e.g. Mac with Apple Silicon / M-series, Intel Mac, Windows, or Linux) 2. Am I running this directly on that OS, or inside a virtual machine (e.g. Kali Linux in VMware/VirtualBox)? 3. Do I already have Docker installed and working? Wait for my answers, then tailor everything to my environment. THINGS TO ACCOUNT FOR ONCE YOU KNOW MY SETUP: Pin the cluster's Kubernetes version to match my kubectl, to avoid version-skew warnings. IF I am on an ARM machine (Apple Silicon, or ARM Linux): warn me that two scenarios (system-monitor and hunger-check) rely on Intel-only tools and will crash-loop — this is a known KIND limitation on ARM, not something to fix. When we reach the access script, help me comment those two scenarios out so it doesn't hang, and skip them. IF I am on an Intel/x86 machine, this doesn't apply and all scenarios should run. Some tools (like git-dumper) may need installing via pipx. Start by asking me the setup questions above, then wait for my answers.