An intentionally vulnerable Kubernetes cluster environment for hands-on security training and practice.
Kubernetes Goat is an intentionally vulnerable Kubernetes cluster environment designed for security training. It provides a safe, interactive playground where users can practice attacking and defending against real-world Kubernetes security misconfigurations. The project includes multiple pre-built scenarios covering common vulnerabilities like sensitive data exposure, container escapes, and privilege escalations.
Security professionals, DevOps engineers, and developers who work with Kubernetes and want to build practical security skills through hands-on exploitation and defense exercises.
It offers a curated, ready-to-deploy vulnerable environment that eliminates setup complexity, allowing learners to focus immediately on practicing offensive and defensive Kubernetes security techniques in a controlled, legal setting.
Kubernetes Goat is a "Vulnerable by Design" cluster environment to learn and practice Kubernetes security using an interactive hands-on playground 🚀
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes 22+ pre-configured scenarios covering key attack vectors like container escapes, SSRF, and RBAC misconfigurations, as listed in the README.
Bundles popular tools like KubeAudit, Falco, and Cilium Tetragon for auditing and monitoring demonstrations, providing a complete learning ecosystem.
Offers setup guides for GKE, EKS, AKS, K3S, and KIND, ensuring flexibility across different Kubernetes deployments.
Emphasizes interactive exploitation with step-by-step documentation, aligning with its philosophy of learning through controlled experimentation.
Requires cluster admin privileges and installation of kubectl and helm, which can be a barrier for users without prior cluster management experience.
Includes scenarios like 'Helm v2 tiller' marked as deprecated, potentially teaching practices that are no longer relevant in modern Kubernetes.
Running multiple vulnerable services and integrated tools can consume significant CPU and memory, as hinted in the DoS scenario, making it heavy for local setups.