Hi, Unfortunately, there won't be native support for Kubernetes in Flink 1.5 yet [1]. That is, you will still have to deploy a standalone session cluster and submit a job via the REST API.
Can you open an issue in JIRA regarding the Blob Cache corruption? FLINK-5908 is closed already. Best, Gary [1] http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Migration-to-Flip6-Kubernetes-tp18937p19132.html On Mon, May 7, 2018 at 7:48 PM, anaray <anum...@gmail.com> wrote: > Thank You Fabian. We are looking forward for this feature, especially a way > to bundle the job jar along with the container (even in taskmanagers). > > In production we deploy flink (1 job=1 cluster) in Docker Swarm. One of the > main issue we face is related to blob download when the taskmanager fails > and restarts . Occasionally we run into blob corruption issue, and job > fails > ( FLINK-5908 <https://issues.apache.org/jira/browse/FLINK-5908> ). This > prompted us to monitor job and resubmit the job again using automated > scripts! Since, we go with 1 cluster = 1 job, we can bundle the job jar, > and > totally avoid the blob downloads, and automate the deployment & management > of job life-cycle. And we are planning to move to Kubernetes shortly > > > > Best, > > > > -- > Sent from: http://apache-flink-user-mailing-list-archive.2336050. > n4.nabble.com/ >
