Every time you ship a Java service to Kubernetes, you ship a base image: dependencies, a JDK and an OS layer. None of which you wrote besides your code, but all of which you must monitor and patch. The real artifact you care about, your application JAR and its dependencies, are buried inside 250 MB of packaging you never wanted to own. WebAssembly already solved this. With KWasm, the Wasm runtime lives on the node, the developer ships only a .wasm module as an OCI artifact, a RuntimeClass tells Kubernetes to execute. No Dockerfile, no container images involved at all.

In this talk we walk through how the SpinKube analogy actually maps cleanly to Java; what containerd shims, node provisioners, and CRDs can do: build your own Kubernetes-based platform, and quite easily with agentic AI.