That's good, but you should probably stop and consider whether the discussions that led up to this document's creation could have taken place on this dev list -- because if they could have, then they probably should have as part of the whole spark-on-k8s project becoming part of mainline spark development, not a separate fork.
On Mon, Feb 5, 2018 at 1:17 PM, Matt Cheah <mch...@palantir.com> wrote: > Hi everyone, > > > > While we were building the Spark on Kubernetes integration, we realized > that some of the abstractions we introduced for building the driver > application in spark-submit, and building executor pods in the scheduler > backend, could be improved for better readability and clarity. We received > feedback in this pull request <https://github.com/apache/spark/pull/19954> > in particular. In response to this feedback, we’ve put together a design > document that proposes a possible refactor to address the given feedback. > > > > You may comment on the proposed design at this link: > https://docs.google.com/document/d/1XPLh3E2JJ7yeJSDLZWXh_ > lUcjZ1P0dy9QeUEyxIlfak/edit# > > > > I hope that we can have a productive discussion and continue improving the > Kubernetes integration further. > > > > Thanks, > > > > -Matt Cheah >
