Enterprise DevSecOps & GitOps Platform
Manual deployments, inconsistent security scanning, and slow CI/CD pipelines cause high failure rates in production and drastically slow down developer velocity.
The thesis: How do we enforce strict security and quality gates without creating friction that slows down engineering velocity?
Built a deployment pipeline using Jenkins, running jobs in parallel and dropping Docker build times using layer caching. Set up Quality Gates that instantly block code from deploying if it has less than 80% test coverage or contains critical bugs.
Integrated SonarQube, OWASP, and Trivy to scan code and containers before staging. Automated deployments with ArgoCD, configured to check the Git repository every 3 minutes and auto-revert any manual server changes to match Git state.
Built Grafana dashboards to track engineering speed (DORA metrics) and system reliability (SLOs). Sent all server logs to a central ELK Stack instead of making engineers manually search through individual containers.
ArgoCD Sync Drift
If an engineer manually edits a resource in the EKS cluster (e.g., via `kubectl edit`), ArgoCD will immediately detect the state drift against Git and auto-revert the manual change during its next 3-minute reconciliation loop. Git remains the sole source of truth.
Jenkins Cache Invalidation
If foundational Docker layers (like `package.json` or `requirements.txt`) change, the cache invalidates entirely. This drastically spikes build times for that specific run, demonstrating why caching optimization requires disciplined dependency management.
Pipeline Execution
Methodology
Parallel execution effectively reduces overall CI/CD time.
Docker Build Time
Methodology
Effective use of layer caching speeds up container builds.
Prod Security Issues
Methodology
Shift-left security prevents known vulnerabilities from reaching production.