Cluster App: Fall, Winter and Spring
Three blog seasons that build and then grow a photo-checking chore app on top of my EKS + GitOps home lab. Fall builds the minimum viable product. Winter makes it reliable under pressure. Spring makes it smarter, opens it to more people and measures what it costs. Each season starts by changing the chores through Git and ends by comparing itself to the seasons before.
Before Fall Cleaning #0 (this week)
- Merge the pending say_when_infra and say_when_git_ops patches. EKS 1.31 leaves extended support on Nov 26, 2026, so the cluster should be on 1.35 first.
- Take the photos now while the leaves are still down: a good and a "wrong" shot for each of the 10 chores. They become the test set for every later part.
- Photograph every snowfall from December through February: shoveled, unshoveled, salted, and a few wrong shots. Winter is built from these.
- Start registering a phone number for texts with AWS during the winter. Approval can take weeks, and Winter #5 needs it.
Hours include building, debugging and writing each post. Dates assume about 8 hours a week on evenings and weekends, with Thanksgiving and the holidays as lighter weeks. Some components show up twice on purpose, for example kube-bench as a "before" snapshot in Fall #0 and an "after" in the Fall finale, or texts arriving in Winter after email in Fall. That repetition is the progression story.