#Argo CD

3 posts

My Kubernetes App Moved to EKS Unchanged. Everything Around It Didn't.

I moved the application and delivery contract from my home k3s server to temporary EKS infrastructure. The workload stayed familiar, but AWS introduced new decisions around networking, identity, compute and load balancing. I tested the complete path, measured drift correction and then removed the environment.

September 11, 2026Building a Kubernetes Delivery Platform

#Kubernetes#EKS

Argo CD Fixed My Drift, Then Deployed My Bad Release

I first built an always-on k3s lab, then discovered that a successful rollback could leave its saved YAML behind. After designing a safer GitOps path, I implemented it and tested three real behaviors: drift correction, a correctly deployed bad release, and durable recovery through a Git revert.

September 3, 2026Building a Kubernetes Delivery Platform

#Kubernetes#GitOps

The Rollback Worked. My Next Deploy Could Break It Again.

My Kubernetes rollback restored Version 2, but it did not update the YAML that still declared Version 3. I corrected the file manually, then designed a delivery process in which Git recorded the chosen version and the cluster followed it automatically.

August 27, 2026Building a Kubernetes Delivery Platform

#Kubernetes#GitOps