It sounds like you underestimate the enthusiasm for miniatures in general. There is a lot of demand for finely printed models––look at Tribes on MyMiniFactory, or the success of primarily 3D printed games like Trench Crusade.
On the other side of this _is_ the affordability of 3D printed miniatures. The linked-to article is salient/cogent/great, but the secondary topic at hand––lowering the price of entry for miniatures-based table top gaming––is still salient. 3D printing won't necessarily upend GW's business model, but it does provide an entry point that is more affordable by some calculus.
Author of post here and CRL employee: just for some additional detail, we reached out to Kelsey about the problems he's seen running databases in Kubernetes.
He said "You still need to worry about database backups and restores. You need to consider downtime during cluster upgrades."
These things are totally true. K8s doesn't automate backups (edit: by default; though, it can) and if you need to take K8s down for upgrades, then everything is down. For its part, though, CockroachDB supports rolling upgrades with no downtime on Kubernetes.
As for routing, that is tough problem if you want to run K8s across multiple regions, though we have some folks who've done it.
Databases are just applications with different resource needs. Please stop pushing forward the notion that they can't be run in containers or container orchestration systems. Databases are just programs. If the substrate for running your containers doensn't reliably support flock or fsync or something your database needs, then maybe pick a better substrate that does -- container runtimes these days and kubernetes don't stand in your way these days.
Well with k8s 1.10+ it's also possible to use statefulsets and local volume, so with affinity it's possible to just use k8s as an orchestration system where you "install" your database and keep it up to date with k8s. of course if a node goes down you need to failover, etc. but patroni/zalando postgres works really well with statefulsets and local volume. (as long as a single node is still running, which should always be the case...)
(https://kubernetes.io/blog/2018/04/13/local-persistent-volum...)
I want to note that this has actually been possible since like k8s 1.7, you can just start a DB with node affinity and use hostPath volumes.
That's what I was doing until rook came around. If you're running in something like AWS (or even if you're not), you can also do something like attach an EBS volume (to a local host) and do that. Or, you can set up a plain ISCSI drive (or get one from your provider, even basic providers these days might offer storage that way) and use that.
On the other side of this _is_ the affordability of 3D printed miniatures. The linked-to article is salient/cogent/great, but the secondary topic at hand––lowering the price of entry for miniatures-based table top gaming––is still salient. 3D printing won't necessarily upend GW's business model, but it does provide an entry point that is more affordable by some calculus.