Github user foxish commented on the issue:
https://github.com/apache/spark/pull/19354
> We don't see much in the way of Kubernetes pull requests against Spark.
Can you elaborate on exactly what you mean by "it's being integrated now"?
@rcgenova, we're working with @felixcheung, @rxin and testing
infrastructure folks from RISELab - getting our CI testing setup, addressing
feedback on PRs, simplifying them into appropriate reviewable chunks that can
be sent up here, and [stabilizing the
release](http://apache-spark-user-list.1001560.n3.nabble.com/Announcing-Spark-on-Kubernetes-release-0-4-0-td29370.html)
for the existing audience in our own repo -
https://github.com/apache-spark-on-k8s/spark/.
@srowen, @mridulm, I understand your concern here and it is definitely a
valid one. When the note was added for Kubernetes, it was made clear to us that
this is **not** meant to offer a path to an upstream merge
(https://github.com/apache/spark/pull/17522#pullrequestreview-30716000), but to
help build the consensus, community maintainership and adoption required for
our own separate fork. TBH, we didn't see the doc note have a credible impact
on the activity we saw on our fork. Around 2% of the visits to our docs/repo
came with a spark.apache.org referer, which may validate your opinion that
adding into the docs did not really meet its purpose -- even for us.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
