Welcome to my GitHub profile! I started my career engineering steel hulls and shipyard automation systems β where a miscalculation could sink something worth millions. That instinct for precision, resilience, and systematic thinking is what I brought into cloud architecture. Today I design infrastructure that doesn't sink either: automated, observable, recoverable systems built for teams that need to move fast without breaking things. Every repo on this profile is a solved problem, a lesson documented, or a concept pushed until it clicked.
|
Expected Completion: Q2 2026 Expected Graduation: 2027 |
Status: Implementing ArgoCD & Flux Status: Building Reusable Terraform Modules |
Most DevOps engineers come from software development. I came from shipbuilding β and I think that's made me a different kind of engineer.
|
Graduated with a Diploma in Shipbuilding Technology. Spent three years in an environment where precision isn't a preference β it's a structural requirement. My first real automation work happened on a shipyard floor, not a server rack: streamlining CAD/CAM workflows and documenting complex manufacturing systems for teams that couldn't afford ambiguity. What I actually did...β’ Led technical documentation and multi-stage design review processes β’ Identified and automated repetitive engineering workflows β’ Collaborated with cross-functional teams across planning, production, and QA β’ Developed fluency in CAD/CAM tooling and production scheduling systems |
While still working in engineering, I taught myself Python and Shell scripting at nights and weekends. Built internal tools that cut documentation processing time by 40%. That number got attention β and it confirmed that automation could be my full-time work, not just a side project. I left engineering behind and didn't look back. What I actually did...β’ Mastered Linux system administration and Bash scripting alongside a full-time role β’ Completed AWS fundamentals certifications to validate early cloud knowledge β’ Built workflow automation tools adopted by colleagues with no software background β’ Started contributing to open-source projects to learn from real production codebases |
|
Made the full transition into DevOps. Enrolled in the DevOps Career Track Season 2 by Poridhi for structured, hands-on depth alongside real project work. Previously drove enterprise-level cloud migration projects achieving 60% faster deployment cycles. Every project on this GitHub reflects real implementation β not tutorials, not templates, not copy-pasted YAML. What I actually did...β’ Architected multi-cloud infrastructure across AWS, GCP, and Azure β’ Deployed production K3s and EKS clusters on AWS using Terraform IaC β’ Built Jenkins CI/CD pipelines with distributed agent configuration on AWS β’ Implemented K8s autoscaling, rolling updates, and StatefulSet management β’ Configured Docker-based monitoring stacks with automated alerting |
Pursuing a Bachelor's in Computer Science (Cloud Computing) while preparing for the AWS Solutions Architect Associate exam. My learning style is hands-on first: I build the thing, break it, rebuild it better, then write about it. That's what the repos and blog posts are β documented evidence of the process. What I'm actively doing...β’ Writing technical deep-dives on Kubernetes, Docker, and cloud architecture β’ Maintaining an automated LeetCode solutions system with analytics β’ Building GitOps lab environments with ArgoCD and Flux β’ Studying distributed systems and advanced AWS architecture patterns β’ Contributing to cloud-native open-source projects |
"A ship is built to survive storms, not avoid them. Good infrastructure works the same way."
|
Enterprise-grade Kubernetes infrastructure on AWS EKS, designed for multi-environment production deployments. Implements a complete IaC stack covering cluster provisioning, node group management, IAM role binding, and network policies β built to be cost-effective without sacrificing scalability or reliability. |
Production-ready K3s lightweight Kubernetes cluster on AWS, fully automated through Terraform. A complete infrastructure-as-code blueprint covering EC2 provisioning, VPC networking, and K3s cluster bootstrapping β demonstrating that lightweight doesn't mean cutting corners on production readiness. |
|
Hands-on implementation of Kubernetes Horizontal Pod Autoscaler β the mechanism that separates truly elastic systems from ones that just claim to be. Builds a real workload, fires synthetic traffic at it, and watches the cluster respond: pods scale out under load, scale back when it clears. Includes metrics-server setup and threshold tuning. |
Implementation of zero-downtime deployment strategies using Kubernetes rolling updates and rollbacks. Covers maxSurge/maxUnavailable tuning, readiness probe configuration, and rollback execution β the real ops work that keeps services alive through deployments. Includes failure simulation and controlled recovery. |
|
Comprehensive Jenkins CI/CD implementation from bare infrastructure to a fully operational distributed build environment. Covers automated server provisioning on AWS, controller-agent architecture configuration, job management, and enterprise-grade automation practices β the full pipeline lifecycle, not just a hello-world pipeline. |
A multi-container system where NGINX doesn't just run β it's watched. A dedicated watcher container continuously polls the server's health; on failure, a mailer container fires an automated alert instantly. A clean, composable implementation of the sidecar monitoring pattern that reflects how production observability actually works at the container level. |

