Is it possible to avoid dynamic classloading when using the operator with a native kubernetes application deployment?
If I put the job jar into /opt/flinklib, then there are two possible outcomes: 1. If I point jarURI to the jar, I get linkage errors (presumably: the class have already been loaded by the AppClassLoader and the FlinkUserCodeClassLoader). 2. If I do not include jarURI the operator pods encounter a NullPointerException. The docs state this is optional, but appears to only pertain to standalone mode. https://issues.apache.org/jira/browse/FLINK-29288 enabled the optional jarURI (apparently only for standalone deployments). Are there any additional configurations (configs, jar locations, etc) that are needed to avoid dynamic classloading in this case?
