Well, yes and no.
By using Kubernetes, you get a scalable infrastructure. By using OTP/Akka, you get a scalable application.
While there is common problems to both domains, they are still 2 different domains.
For example, using only Kubernetes, you won't have the ability to react to a Pod restart within your application (unless your application is aware of Kubernetes).
Using only OTP/Akka, you still need a workflow for deployment and infrastructure management, and you still need to implement node discover for clustering.
NB: For Elixir, you have libcluster[1] that can use different strategies for node discovery, including using a Kubernetes Service to discover the nodes (as Pods).
EDIT: Using Kubernetes, libcluster, and Horde[2], you get the best of both worlds IMHO.
I find it very useful because "Distributed OTP Application" are a pain IMHO (they must be started during the boot of the BEAM).
[1] - https://en.wikipedia.org/wiki/Conflict-free_replicated_data_...