The main difference sadly break most of the analogy. Because a pod is far from the granularity of a process. It is closer to the granularity of an application,

The main difference sadly break most of the analogy. Because a pod is far from the granularity of a process. It is closer to the granularity of an application, the biggest abstraction that OTP gives you. What that mean is that k8s does not have the same property than erlang. In erlang, isolation is your go to tool. If you need something, you spawn a process. Having a lot of really granular process makes scheduling on cores easy, makes your design easy to crash because the blast area is small, and makes it really cheap to have message passing in the core of the VM. In k8s, any networking is hard, hence the current trend of service mesh. As the unit of computation is bigger, supervision get harder. Building a supervision tree is more expensive. And crashing and restarting get more expensive too. K8s has the advantage of being language agnostic ofc. But do not forget the paradigm shift that having really cheap process give you in an integrated environment like the BEAM. And ofc, i have not even talked about the dynamic tracing that the BEAM gives.