Projects

Identified recurring patterns in customer support tickets at CloudKeeper and built automation around them. Created EKS review questionnaires, upgrade scripts, DQI tracking sheets, and standardized customer-facing documentation. Impact: Reduced time spent on common EKS issues Standardized customer review and upgrade processes Built reusable scripts for multi-version EKS upgrades Created internal KB articles to reduce repeated questions Tools: Bash, Python, Kubernetes, EKS

Led cost optimization engagements across 50+ customer environments at CloudKeeper. Worked on right-sizing pods, tuning VPA/HPA configurations, implementing Karpenter with optimal bin-packing, and moving eligible workloads to spot instances. Key results: Reduced one customer’s monthly bill by $20K on a $111K/month account (18% savings) Saved a logistics platform $15K+/month through EKS and Karpenter optimization Standardized cost review questionnaires and savings tracking across the team Tools: EKS, Karpenter, VPA, HPA, KEDA, Helm, Terraform ...

EKS upgrades across multiple Kubernetes versions are complex, especially in production environments with custom networking, service meshes, and stateful workloads. Built comprehensive upgrade tooling and documentation that was used across multiple customer engagements. What I built: Step-by-step upgrade scripts with pre-flight checks Rollback procedures for each upgrade stage Documentation covering add-on compatibility, API deprecations, and breaking changes Deep dives into Kubernetes 1.34 and 1.35 feature changes Tools: EKS, Kubernetes, Bash, Terraform ...

Karpenter efficiently provisions nodes to match pod requests, but if developers request 4 CPUs for a pod that uses 0.2 CPUs, Karpenter will buy a node to fit that bloated request. It bin-packs waste, but it cannot fix the waste itself. Built an internal scheduling component that optimizes at the scheduling stage itself, not just at provisioning. Ran 14 internal iteration cycles to find the optimal bin-packing strategy that accounts for actual resource utilization, not just requested resources. ...

Took a monolithic PHP-based supercar auction platform and broke it into containerized services running on EKS. The platform included Moodle for training modules and Nginx as the web layer. What I did: Containerized 40+ microservices from bare-metal/VM setup Deployed on EKS with proper scaling, health checks, and resource limits Set up CI/CD pipeline for automated builds and deployments Configured monitoring and alerting Tools: EKS, Docker, Terraform, GitHub Actions, Nginx, PHP, Moodle ...

At MicroTechnologies, built a reusable infrastructure deployment system using multi-module Terraform and CI/CD pipelines. New customer projects could be onboarded with a standardized setup that included networking, compute, container orchestration, monitoring, and security. What it covered: Multi-environment Terraform modules (dev, staging, production) ECS/EKS cluster setup with proper IAM, networking, and security groups Monitoring stack (Grafana, Prometheus, New Relic) CI/CD pipeline templates for GitHub Actions and Jenkins Tools: Terraform, Terragrunt, AWS, GitHub Actions, Jenkins ...