Github user foxish commented on a diff in the pull request:

    https://github.com/apache/spark/pull/20314#discussion_r162430012
  
    --- Diff: docs/running-on-kubernetes.md ---
    @@ -41,11 +45,10 @@ logs and remains in "completed" state in the Kubernetes 
API until it's eventuall
     
     Note that in the completed state, the driver pod does *not* use any 
computational or memory resources.
     
    -The driver and executor pod scheduling is handled by Kubernetes. It will 
be possible to affect Kubernetes scheduling
    -decisions for driver and executor pods using advanced primitives like
    -[node 
selectors](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector)
    -and [node/pod 
affinities](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
    -in a future release.
    +The driver and executor pod scheduling is handled by Kubernetes. It is 
possible to schedule the
    +driver and executor pods on a subset of available nodes using a [node 
selector](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector)
    +using the configuration property for it. It will be possible to use more 
advanced
    --- End diff --
    
    Done


---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to