I have something similar, but simpler that I made for home use. Anything I want to deploy goes in a container, and I have a template directory with a service ya

I have something similar, but simpler that I made for home use. Anything I want to deploy goes in a container, and I have a template directory with a service yaml, a deployment yaml, an ingress yaml and maybe some PVCs. Really what you're aiming for is avoiding the repetitive tedium of writing out the same thing over and over for what essentially is a simply container that needs an ingress for web/api access and perhaps some storage or access to a DB. It's overkill for sure, but I don't want to run Docker hosts, and I don't (yet) have anything in my clusters that will let my just run a container and provide an ingress for it without this; plus I prefer the declarative approach anyway and I can just commit it to my local git for when I need it.