search

GoogleCloudPlatform / flink-on-k8s-operator

[DEPRECATED] Kubernetes operator for managing the lifecycle of Apache Flink and Beam applications.
Apache License 2.0
658 stars 265 forks source link

Separate job client Docker image and Flink JobManager/TaskManager image #15

Closed functicons closed 4 years ago

functicons commented 5 years ago

Currently, the Flink job client runs as a Kubernetes job, which uses the same container as the Flink JobManager and TaskManager. There is a benefit of separate the two. Some functionalities such as downloading remote Job jar can be supported in the job client image, while using the official Flink image for JM/TM.

We could create a dedicated Docker image for the job client, we could also use the operator image (by adding the capability of job submission) for the job client. The latter approach seems to be easier to manage for end users.

functicons commented 4 years ago

It is not needed anymore we generated a submit_job.sh and mounted into the job submitter container.