> Kubernetes does not solve the issue, it merely has strategies for how to upgrade nodes. The issue is that... I understand the issue, Gleam/Caramel/et al. (st

> Kubernetes does not solve the issue, it merely has strategies for how to upgrade nodes. The issue is that... I understand the issue, Gleam/Caramel/et al. (static typing layers on BEAM) are not trying to solve this issue. > So my assumption here is that they're putting ocaml on the BEAM to utilize OTP and clustered apps, correct? That's actually not my assumption. I'm assuming that the point of Caramel is to get sound static typing for (some of) the code that we are deploying on the BEAM. It doesn't necessarily have to be for clustered apps. As I said, many deploys of even Erlang and Elixir today are not using clustered nodes. They don't care about those capabilities. They use Kubernetes to manage nodes and state. > instead it seems like you'd be forced to spin up entirely new clusters and then direct traffic to the new cluster to bypass this problem. This is exactly what Kubernetes (or Nomad etc.) will let you avoid--they can spin up and spin down nodes within the same cluster.