Re: Running JobManager as Deployment instead of Job

Posted by Till Rohrmann on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Running-JobManager-as-Deployment-instead-of-Job-tp25927p25948.html

Hi Sergey,

the rationale why we are using a K8s job instead of a deployment is that a Flink job cluster should terminate after it has successfully executed the Flink job. This is unlike a session cluster which should run forever and for which a K8s deployment would be better suited.

If in your use case a K8s deployment would better work, then I would suggest to change the `job-cluster-job.yaml` accordingly.

Cheers,

Till

On Tue, Feb 5, 2019 at 4:12 PM Sergey Belikov <[hidden email]> wrote:

Hi,

my team is currently experimenting with Flink running in Kubernetes (job cluster setup). And we found out that with JobManager being deployed as "Job" we can't just simply update certain values in job's yaml, e.g. spec.template.spec.containers.image (https://github.com/kubernetes/kubernetes/issues/48388#issuecomment-319493817). This causes certain troubles in our CI/CD pipelines so we are thinking about using "Deployment" instead of "Job". 

With that being said I'm wondering what was the motivation behind using "Job" resource for deploying JobManager? And are there any pitfalls related to using Deployment and not Job for JobManager?

Thank you in advance.

--