ikiler commented on issue #10904: URL: https://github.com/apache/dolphinscheduler/issues/10904#issuecomment-1182942664
> > I build the dev , flink still uses yarn by default in application mode , I find the k8s task , but cannot be applied to flink , you can look at this [application mode](https://nightlies.apache.org/flink/flink-docs-release-1.15/zh/docs/deployment/resource-providers/native_kubernetes/#application-mode) Pod creation, operation, and destruction are all operated by flink itself , like this: > > ``` > > ./bin/flink run-application \ > > --target kubernetes-application \ > > -Dkubernetes.cluster-id=my-first-application-cluster \ > > -Dkubernetes.container.image=custom-image-name \ > > local:///opt/flink/usrlib/my-flink-job.jar > > ``` > > > > > > > > > > > > > > > > > > > > > > > > flink will create jobmanager, taskmanager, and copy config .........does many things, So ,simply specifying a image for a k8s task cannot solve the problem. we don't have any path to run a flink task through the k8s tab > > I get your point, they are different way. So it's better to expand flink task to support the k8s deployment modes. @ikiler Are you interested in expanding flink task? like #9577 I'd love to if I could, but I have no good idea to solve it now. we are still using placing the api in the jar and using the history-server api to monitor the app in ds, which is obviously a bad practice -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
