Skip to content

Tetris DevSecOps Kubernetes Pipeline

Level:Advanced
Time:3-5 hours
Cost:high
Works locally:No
Cloud creds:Yes
Cleanup:No
Reviewed:2026-05-30
Validation:npm --prefix Tetris-V1 test --if-present

Tetris apps plus EKS and Jenkins Terraform assets.

Outcome Passing pipeline run plus scan/deploy evidence
Tools used Node.js, Docker, Kubernetes, Terraform, Jenkins, AWS
Best fit Advanced - 3-5 hours
Student workstation Repository files CI/CD pipeline AWS account Validation proof
  • Install or review: Node.js, Docker, Kubernetes, Terraform, Jenkins, AWS.
  • Use your own cloud account credentials and keep them out of commits.
  • This project expects cloud resources, so verify budget alerts and cleanup first.
  • Open the safety guide before running commands that create infrastructure.
Cost and credential stance

Cost risk is high. Cloud target: AWS. Cloud credentials needed: Yes. Always use your own account, never commit secrets, and confirm cleanup before creating paid infrastructure.

Use this flow before you run commands:

  1. Read the cost and credential warning above.
  2. Review the validation, troubleshooting, cleanup, and portfolio proof sections below.
  3. Follow the original project guide preserved near the bottom of this page.
  4. Return to the validation and cleanup checks before you capture portfolio evidence.

Run the project validation command before and after meaningful changes:

Terminal window
npm --prefix Tetris-V1 test --if-present
  • Run npm --prefix Tetris-V1 test --if-present first so local tooling issues are visible early.
  • If a command fails, check tool versions, working directory, and required environment variables.
  • For cloud failures, confirm account identity, region, quotas, and least-privilege IAM.
  • For pipeline failures, check repository secrets, runner permissions, and pinned action versions.

No dedicated cleanup command was detected in the project README. Treat this as a warning: before provisioning anything, write down the exact delete, destroy, or rollback steps for your environment.

  • Validation command output: npm --prefix Tetris-V1 test --if-present
  • Screenshot or terminal proof: Passing pipeline run plus scan/deploy evidence
  • Notes explaining what changed, what failed, and how you fixed it
  • Cleanup evidence, especially for cloud or Kubernetes resources

The original README content is preserved here for lab-specific commands and context. Headings are intentionally demoted so the page outline stays focused on the standard lab flow.

<div class="external-image-reference"> <strong>External image reference</strong> <a href="https://img.shields.io/badge/Connect%20with%20me%20on-LinkedIn-blue.svg" target="_blank" rel="noopener noreferrer">LinkedIn</a> </div> <div class="external-image-reference"> <strong>External image reference</strong> <a href="https://img.shields.io/github/stars/AmanPathak-DevOps.svg?style=social" target="_blank" rel="noopener noreferrer">GitHub</a> </div>
External image reference DevSecOps
External image reference Kubernetes
External image reference Jenkins
External image reference ArgoCD
External image reference Docker
External image reference Terraform

Infrastructure Diagram

Welcome to an immersive DevSecOps learning experience! This project guides you through deploying a Tetris game on AWS EKS while mastering the art of DevSecOps.

🛡️ 2026 DevSecOps Enhancements (What You Will Learn)
Section titled “🛡️ 2026 DevSecOps Enhancements (What You Will Learn)”

This repository’s architecture showcases a mature DevSecOps pipeline deployed to EKS:

  1. Supply Chain Security: We integrate OWASP Dependency-Check into the CI pipeline to actively scan and block deployments that rely on compromised or vulnerable open-source libraries.
  2. Zero-Trust GitOps Delivery: By employing ArgoCD, the deployment model shifts from “push” (where Jenkins holds cluster admin credentials) to “pull”. ArgoCD securely syncs state directly from inside the EKS cluster boundary, drastically reducing the external attack surface.
  1. EKS-TF: Explore Terraform scripts for deploying EKS clusters on AWS.
  2. Jenkins-Pipeline-Code: Jenkins pipeline code for automated CI/CD.
  3. Jenkins-Server-TF: Terraform scripts for provisioning Jenkins servers on AWS EC2.
  4. Manifest-file: Kubernetes manifest files for Tetris application deployment.
  5. Tetris-V1: Initial version of the Tetris game application.
  6. Tetris-V2: Enhanced version of the Tetris game application.
  1. Clone the Repository:

    Terminal window
    git clone <a href="https://github.com/DevCloudNinjas/DevOps-Projects.git" target="_blank" rel="noopener noreferrer">GitHub source link</a>
  2. Explore the Directories: Navigate into each directory to find detailed scripts, pipelines, and configurations.

  3. Follow the Blog: Implementation details and insights are documented in the associated blog post.

  1. Jenkins: Automated CI/CD pipelines
  2. ArgoCD: Continuous deployment to Kubernetes
  3. Kubernetes: Orchestration for containerized applications
  4. Trivy: Container vulnerability scanner
  5. OWASP Dependency-Check: Ensuring secure dependencies
  6. Docker: Containerized application deployment
  7. SonarQube: Unveiling code quality insights
  8. Terraform: Infrastructure as Code for AWS EKS

To implement this project, follow the step-by-step guide in our detailed blog post. Learn how each tool plays a crucial role in achieving DevSecOps excellence.

Special thanks to the open-source community and the contributors who make learning and collaboration an incredible journey.

This project is licensed under the Apache-2.0 license see the LICENSE file for details.

Use the guide first.

The full learning flow stays on this page. Open GitHub only when a step asks you to inspect code, fork the lab, or download source assets.