The Kubernetes do not have a default distributed storage and provide public api to ship files like Yarn local resource. So we could not ship the user jars and files on the client side to jobmanager and taskmanager. Also it is not a common way on Kubernetes. Instead, users usually build their jars and files into the docker image. So when the jobmanager and taskmanager are launched, the users jars already existed.
Even if some users do not want to build the jars into the image, they could use the initContainer to download the jars from the storage(http/s3/etc.).
All in all, the Kubernetes per-job cluster will only support cluster deploy-mode(now called "application mode").
This ticket depends on FLIP-85(Support cluster deployment). Please reference the documentation FLIP-85 for more information.