[
https://issues.apache.org/jira/browse/FLINK-28915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855099#comment-17855099
]
Ferenc Csaky commented on FLINK-28915:
--------------------------------------
[~rmetzger] are you using the default {{flink}} image as {{spec.image}}? I did
not have enough time to verify it completely, but my hunch is that the default
img do not contain the S3 FS plugin, hence the error. I also guess you are
using a modified operator, cause the current operator is compiled against Flink
1.18 and the {{FlinkDeploymentController}} executes and does not even deploy if
the {{jarURI}} scheme is not local. After I compiled the operator with Flink
1.19, I managed to deploy a job successfully via a HTTP served JAR ({{jarURI:
http://host.minikube.internal:9999/data/TopSpeedWindowing.jar}}), so I am
pretty sure the DFS variant should work as well.
> Make application mode could support remote DFS schema(e.g. S3, OSS, HDFS,
> etc.)
> -------------------------------------------------------------------------------
>
> Key: FLINK-28915
> URL: https://issues.apache.org/jira/browse/FLINK-28915
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes, flink-contrib
> Reporter: hjw
> Assignee: Ferenc Csaky
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.19.0
>
>
> As the Flink document show , local is the only supported scheme in Native k8s
> deployment.
> Is there have a plan to support s3 filesystem? thx.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
