tbrockman

Forgive any potential misuse of terminology (not my primary field of expertise), "fully Kubernetes-native stack" here is meant to mean that all services and infrastructure (or as much as possible) are deployed within the cluster itself.

For example, rather than using any AWS/Google managed databases, queues, or caches, deploying open-source varieties using standard Kubernetes objects instead.

If so, does anyone have any useful guides/manifests/charts or advice for setting up and configuring something similar? I have a bunch of old devices I've been steadily repurposing as compute/storage for experimentation at home, and it'd be cool to develop closer to a real world distributed environment without footing as large a bill. I would guess I'm not the first person to have been interested in doing this, so at this point just trying not to duplicate any work if this is already a solved problem.