This is an automated email from the ASF dual-hosted git repository.
srowen pushed a commit to branch branch-3.0
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-3.0 by this push:
new a951d13 [MINOR][DOCS] Fix fabric8 version in documentation
a951d13 is described below
commit a951d1376bec3411eaade1ea55141ddc1793c7f1
Author: Kent Yao <yaooq...@hotmail.com>
AuthorDate: Wed Feb 19 10:47:59 2020 -0600
[MINOR][DOCS] Fix fabric8 version in documentation
### What changes were proposed in this pull request?
fix kubernetes-client version doc
### Why are the changes needed?
correct doc
### Does this PR introduce any user-facing change?
nah
### How was this patch tested?
nah
Closes #27605 from yaooqinn/k8s-version-update.
Authored-by: Kent Yao <yaooq...@hotmail.com>
Signed-off-by: Sean Owen <sro...@gmail.com>
(cherry picked from commit 46019b6e6ce334db4649e269e0ad6e7e4d4ab6c2)
Signed-off-by: Sean Owen <sro...@gmail.com>
---
docs/running-on-kubernetes.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/docs/running-on-kubernetes.md b/docs/running-on-kubernetes.md
index 53b883b..a941b8c 100644
--- a/docs/running-on-kubernetes.md
+++ b/docs/running-on-kubernetes.md
@@ -77,8 +77,7 @@ 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. Communication
to the Kubernetes API is done via fabric8, and we are
-currently running <code>kubernetes-client</code> version <code>4.1.0</code>.
Make sure that when you are making infrastructure additions that you are aware
of said version. It is possible to schedule the
+The driver and executor pod scheduling is handled by Kubernetes. Communication
to the Kubernetes API is done via fabric8. It is possible to schedule the
driver and executor pods on a subset of available nodes through 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
scheduling hints like [node/pod
affinities](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity)
in a future release.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org
