PERSONAL NOTES / TECHNICAL WRITING
I use this space for technical notes, lessons from projects, opinions about engineering, and useful articles I come across. External work is credited and linked to its original source.
Reliable infrastructure is rarely the infrastructure that gets the most attention. My view: the best systems make routine work predictable and make failures understandable.
When a deployment needs someone to SSH into a server, remember a sequence of commands and hope nothing was missed, the process is carrying too much hidden knowledge. Automation moves that knowledge into code.
That does not mean every system needs another tool. It means the important path should be repeatable, observable and documented.
A practical collection of lessons from working through EKS, Helm, ingress, IAM, autoscaling and CI/CD.
Kubernetes makes it easy to describe the desired state, but understanding the networking and identity around that state is just as important. In my project, ingress, IAM and deployment behaviour became the areas where concepts connected together.
The biggest lesson was to troubleshoot from the bottom up: application, container, pod, service, ingress, node and cloud infrastructure.
Cloud architecture, DevOps tools, interview lessons and interesting engineering articles will appear here as I learn and build.