What I'm trying to say, is:
> Nodes are not interchangeable
They don't have to be. You just need to make sure that certain pods run on all nodes that match certain criteria. That can be easily achieved with DaemonSets, taints and tolerations.
> you can't route around breakage (if one point of sale goes down, that's one physical device with a dark screen,
Sure, that's the same regardless of how you deploy software to the POS.
> adding one pod somewhere else won't help)
DaemonSets won't do that, so it's not a problem.
> the networking is mostly useless, zero-downtime impossible (you have only one physical screen to use, can't have two containers grab it during a rolling upgrade)
I believe your argument here is that k8s provides more features than what you need. That can be said about anything, all the way down to the hardware. Surely there's a lot of things the CPU on the POS can do that's mostly useless in this context.
> service discovery is irrelevant unless you are running your database on those cash registers for some reason.
Same as above, I guess...?