Yeah, I'm not seeing it, either. Kubernetes' scope is right in the name: control loops. K8s is basically a super powerful IFTTT engine: it looks at state, looks

Yeah, I'm not seeing it, either. Kubernetes' scope is right in the name: control loops. K8s is basically a super powerful IFTTT engine: it looks at state, looks at spec, and figures out how to jigger the system until state matches spec. It has nothing a priori to do with containers, it just happened to be written in service of that space. You could use k8s to run your teakettle. It's like saying QEMU is the new Systemd; it doesn't even make sense, it's a category error.