David Peacock created FLINK-40677:
-------------------------------------
Summary: Native application submission without jarURI fails in
bundled Flink client
Key: FLINK-40677
URL: https://issues.apache.org/jira/browse/FLINK-40677
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Reporter: David Peacock
[FLINK-33926|https://issues.apache.org/jira/browse/FLINK-33926] supports
running native Kubernetes applications from the image’s system classpath
without a submitted JAR. The operator’s older bundled client still blocks this
path, even when the target runtime contains the fix.
*Setup:* downstream Operator {{{}1.15-SNAPSHOT{}}}, embedded Flink client
{{{}1.20.1{}}}, target runtime based on Flink {{{}2.3.0{}}}.
With the application in {{{}/opt/flink/lib{}}}, an explicit
{{{}job.entryClass{}}}, and no {{job.jarURI}} or inherited
{{{}pipeline.jars{}}}, the client fails before JobManager creation:
* Absent {{{}pipeline.jars{}}}: {{NullPointerException}} in
{{KubernetesUtils.checkJarFileForApplicationMode()}} at
{{{}configuration.get(PipelineOptions.JARS).stream(){}}}.
* Empty list: {{{}IllegalArgumentException: Should only have one jar{}}}.
Reproduced through the real upstream {{1.20.1}} native descriptor with
Kubernetes calls stubbed.
*Expected:* classpath-only submission for compatible runtimes, avoiding
redistribution of an application JAR already present in the image.
Could the operator consume fixed client code, with regression coverage through
the real native descriptor?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
