[
https://issues.apache.org/jira/browse/SPARK-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731626#comment-15731626
]
Sean Owen commented on SPARK-18278:
-----------------------------------
Generally, ASF projects produce source not binaries, but, certainly also
publish binary artifacts as a convenience. A docker image falls into that
category. The drawback -- and it's really not trivial -- is that it means we
are distributing a bunch more third party software and now have to police the
license of everything in that image. That alone may be a deal breaker depending
on what exact bits must be distributed.
Aside from that the question is maintenance burden vs convenience for users. I
think ASF projects don't generally distribute 'packagings' but do distribute
binary forms of source artifacts. For example, Spark doesn't publish RPMs or VM
images.
> Support native submission of spark jobs to a kubernetes cluster
> ---------------------------------------------------------------
>
> Key: SPARK-18278
> URL: https://issues.apache.org/jira/browse/SPARK-18278
> Project: Spark
> Issue Type: Umbrella
> Components: Build, Deploy, Documentation, Scheduler, Spark Core
> Reporter: Erik Erlandson
> Attachments: SPARK-18278 - Spark on Kubernetes Design Proposal.pdf
>
>
> A new Apache Spark sub-project that enables native support for submitting
> Spark applications to a kubernetes cluster. The submitted application runs
> in a driver executing on a kubernetes pod, and executors lifecycles are also
> managed as pods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
