It seems like a more accurate comparison would be container images and webassembly. Kubernetes is a orchestrator that tells containers where to run, how many, etc. For WebAssembly to replace Kubernetes, enterprises would need some other orchastration engine - or conceivably, Kubernetes could run webassembly packages in addition to container images.
“Despite the excitement about Wasm and WASI, it should be clear that containers are the major workload in K8s, and for good reason. No one will be replacing the vast majority of their workloads with WebAssembly. Our usage so far makes this clear. Do not be confused by having more tools at your disposal.”
There is a node image you can use to run web assembly. Assuming everything you do is web assembly then using that as a base image would cut down the amount of downloads that'd have to happen for new applications.
