Dear all,

I am trying to implement a Rest client for Flink to send jobs via Restful Flink 
services. And also I want to integrate Flink and Kubernetes natively. I have 
decided to use "Application Mode" as deployment mode according to Flink 
documentation .
I have already implemented a job and packaged it as jar. And I have tested it 
on Standalone Flink. But my aim is to move on Kubernetes and deploy my 
application in Application mode via Rest API of Flink.

I have already investigated the samples at Flink documentation - Native 
Kubernetes<https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/resource-providers/native_kubernetes/#native-kubernetes>.
 But I cannot find a sample for executing same samples via Restful services 
(esp. how to set --target kubernetes-application/kubernetes-session or other 
parameters).

In addition to samples, I checked out the Flink sources from GitHub and tried 
to find some sample implementation or get some clue.
I think the below ones are related with my case.

-          org.apache.flink.client.program.rest. RestClusterClient

-          org.apache.flink.kubernetes. KubernetesClusterDescriptorTest. 
testDeployApplicationCluster

But they are all so complicated for me to understand below points.

-          For application mode, are there any need to initialize a container 
to serve Flink Rest services before submitting job? If so, is it JobManager?

-          For application mode, how can I set the same command line parameters 
via Rest services?

-          For session mode, in command line samples, kubernetes-session.sh is 
executed before job submission to initialize a JobManager container. How sould 
I do this step via Rest client?

-          For session mode, how can I set the same command line parameters via 
Rest services? Although the command line samples send .jar job as parameter, 
should I upload jar before submitting job?

Could you please provide me some clue/sample to continue my implementation?

Best regards,
Burcu
Bu e-posta ve i?eri?i ki?iye ?zel ve gizli bilgiler i?erebilir. E?er mesaj?n 
muhatab? veya muhataba iletmekle y?k?ml? yetkili temsilcisi siz de?ilseniz, bu 
mesaj? ?o?altmak, da??tmak, a??klamak dahil olmak ?zere herhangi bir suretle 
kullanmaman?z gerekti?ini, aksine davran???n?z?n hukuka ayk?r?l?k te?kil 
edebilece?ini bildiririz. E?er bu mesaj? yanl??l?kla ald?ysan?z, l?tfen 
g?ndericiye e-posta ile bildirerek siliniz. Bu mesajda belirtilen ?ahsi 
g?r??ler g?ndericiye aittir ve SDT A.?.'nin resmi g?r???n? temsil etmeyebilir.

This email and its contents may contain information that is privileged and 
confidential. If you are not an intended recipient,or the agent responsible for 
delivering this email to the intended recipient, you are hereby notified that 
any use, dissemination, distribution, or copying of this communication is 
strictly prohibited and may be unlawful. If you received this email in error, 
please notify the sender by replying to this email and delete the email sent in 
error. Personel opinions presented in this e-mail message are solely those of 
the author and do not necessarily represent SDT A.S.`s formal and authorized 
views.

Reply via email to