[SPARK-30371][K8S] Add spark.kubernetes.driver.master conf#27029
[SPARK-30371][K8S] Add spark.kubernetes.driver.master conf#27029wackxu wants to merge 1 commit intoapache:masterfrom
Conversation
|
/assign @liyinan926 |
|
@liyinan926 Could you take a look at this? |
|
@dongjoon-hyun Could you take a look at this? |
|
Thank you for pinging me, @wackxu. |
|
ok to test |
resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/Config.scala
Outdated
Show resolved
Hide resolved
|
Test build #116537 has finished for PR 27029 at commit
|
dongjoon-hyun
left a comment
There was a problem hiding this comment.
One additional request is the following.
- Please remove "refer kubeflow/spark-operator#706" from the PR description.
You had better make this PR complete by itself and you can do.
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
9091a3d to
1cc2de5
Compare
|
Test build #116838 has finished for PR 27029 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/Config.scala
Outdated
Show resolved
Hide resolved
|
Hi, @wackxu Could you address @liyinan926 's comments? |
1cc2de5 to
3c0d369
Compare
|
Test build #117000 has finished for PR 27029 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
3c0d369 to
a8cb113
Compare
|
Test build #117003 has finished for PR 27029 at commit
|
@liyinan926 @dongjoon-hyun Sorry for the deplay, updated. |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
The only failure in K8S integration tests is the following, but it's known to be flaky in these days. |
dongjoon-hyun
left a comment
There was a problem hiding this comment.
+1, LGTM. Thank you, @wackxu and @liyinan926 .
Merged to master.
|
@wackxu . You are added to the Apache Spark contributor group. Congratulation! |
|
@dongjoon-hyun @liyinan926 Thank you for your patient response and detailed review. |
### What changes were proposed in this pull request? make KUBERNETES_MASTER_INTERNAL_URL configurable ### Why are the changes needed? we do not always use the default port number 443 to access our kube-apiserver, and even in some mulit-tenant cluster, people do not use the service `kubernetes.default.svc` to access the kube-apiserver, so make the internal master configurable is necessary。 ### Does this PR introduce any user-facing change? user can configure the internal master url by ``` --conf spark.kubernetes.internal.master=https://kubernetes.default.svc:6443 ``` ### How was this patch tested? run in multi-cluster that do not use the https://kubernetes.default.svc to access the kube-apiserver Closes apache#27029 from wackxu/internalmaster. Authored-by: xushiwei 00425595 <xushiwei5@huawei.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
### What changes were proposed in this pull request? make KUBERNETES_MASTER_INTERNAL_URL configurable ### Why are the changes needed? we do not always use the default port number 443 to access our kube-apiserver, and even in some mulit-tenant cluster, people do not use the service `kubernetes.default.svc` to access the kube-apiserver, so make the internal master configurable is necessary。 ### Does this PR introduce any user-facing change? user can configure the internal master url by ``` --conf spark.kubernetes.internal.master=https://kubernetes.default.svc:6443 ``` ### How was this patch tested? run in multi-cluster that do not use the https://kubernetes.default.svc to access the kube-apiserver Closes apache#27029 from wackxu/internalmaster. Authored-by: xushiwei 00425595 <xushiwei5@huawei.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
What changes were proposed in this pull request?
make KUBERNETES_MASTER_INTERNAL_URL configurable
Why are the changes needed?
we do not always use the default port number 443 to access our kube-apiserver, and even in some mulit-tenant cluster, people do not use the service
kubernetes.default.svcto access the kube-apiserver, so make the internal master configurable is necessary。Does this PR introduce any user-facing change?
user can configure the internal master url by
How was this patch tested?
run in multi-cluster that do not use the https://kubernetes.default.svc to access the kube-apiserver