is there absolutely no way - in native k8s mode - ...
# troubleshooting
t
is there absolutely no way - in native k8s mode - to have the job jar be part of the classpath? must it always be dynamically loaded?