k8s is interesting because its an enabling technology that also wraps tons of other complexity under its name. The execution model is straightforward enough but

k8s is interesting because its an enabling technology that also wraps tons of other complexity under its name. The execution model is straightforward enough but the networking model is complex for anyone not already familiar with ipvsadm, iptables, routing, layer 2 systems, overlay networks, proxies, dns, etc. Getting it running is actually easy enough to lull people into a sense of accomplishment. But if something goes wrong most teams wont know how to respond other than by restarting something. I really hope we can agree on a simpler abstraction where we trade ease of use for less flexibility.