
Why Build the App Now?
I built the stage. Now it needs a show.
The inception of the blog site was born October 2024 & the cloud infrastructure began in March 2026. The app is necessary now cuz I been building a home lab: an EKS cluster in Terraform, about 30 apps deployed by Argo CD, security tools like Kyverno, Falco and Trivy, and a full monitoring stack with Prometheus, Grafana, Loki, Tempo and Thanos. It’s a great platform w/nothing real running on it.
This series fixes that. Over three seasons I’ll build a real app on the cluster and put every piece of that platform to work. Each post builds on the last, showing the progress made in the plan, the hours and everything that breaks along the way.
Say when. I’m your huckleberry.

Sooooo what does this app do again?
The app hands out household chores and checks that they actually got done.
- It sends a chore, like “rake the leaves”, by email.
- Whoever did it sends back a photo.
- AWS Rekognition looks at the photo and decides: is that a rake in a pile of leaves, or a basketball?
- The result lands in Prometheus, Loki and Tempo, and a Grafana board turns that chore green or red.
It’s a silly premise on purpose. The point is the path a photo takes through the platform: through the front door, into a queue, past an AI check, out to the dashboards. All of it is shipped through GitOps onto a cluster that’s locked down.
The show is booked for 3 seasons…for now
- Each season starts by swapping in new chores with a single pull request (leaves in fall, snow in winter, gardens in spring), and ends with a tagged release and a comparison against the seasons before it.
| Season | Theme | The question it answers | Posts | Dates |
|---|---|---|---|---|
| Fall Cleaning: Build It | The minimum viable product | Can you build it? | 11 | Nov 22, 2026 – Feb 21, 2027 |
| Winter Cleaning: Weather the Storm | Reliability and operations | Can you keep it running when things go wrong? | 7 | Mar 7 – Apr 18, 2027 |
| Spring Cleaning: Grow It | Smarter, more users, cost-aware | Can you improve it and watch the bill? | 5 | May 9 – Jun 6, 2027 |
The Road Map
The whole plan is public: 23 posts, about 168 hours, and a new post every Sunday. By the end of Fall, 32 of the 44 components are in use. By the end of Winter, 41. By the end of Spring, all 44.

The roadmap (earpjennings37.github.io/say_when_app/roadmap) is a living document. After every post I flip that post’s items forward and commit the change, so the repo’s history shows whether I stuck to the plan. Every piece of the stack is tagged by status:
- ✓ Done: already built and running, like the EKS cluster, Karpenter and Thanos
- ~ In progress: built, but needs setup for the app, like Argo CD, Kyverno and Grafana
- ✗ Need to add: new, like Route 53, SQS, Rekognition and Step Functions
I attempted to approach it like a Kanban board w/stories organized in numerical order if I was completly starting from scratch standing up a cluster & an app. W/that said as you see above the columns are done, in-progress, & need to add.

- Done:
- Need an EKS Cluster
- HCP Terraform
- In-Progress:
- Before & After of security w/Kubebench & Popeye
- Image building
- Github pipeline & ArgoCD
- Need to do:
- Budget for costs
The 3 seasons are organized of Fall – “ok just get something set up”, Winter – “looks good, lets strengthen it”, & Spring “put some final touches on this to make it look pretty”. I break each series into phases of approaches to be grouped up w/each tooling applied to the blog-post to see the progress.
- Fall

- Winter

- Spring
