-
Notifications
You must be signed in to change notification settings - Fork 118
Optionally expose the driver UI port as NodePort #131
Optionally expose the driver UI port as NodePort #131
Conversation
Also modify |
Thanks @mccheah for taking a look. Updated |
Can we work out a better scheme for setting the type of the services we create? We have a similar need in #116 as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a short-term addition this certainly gets the job done of exposing the driver UI port to outside the cluster. For longer term I think we might want to have one flag for each service's type, in addition to a flag that controls all of them at once.
I'm not sure we should block this PR on that though.
@foxish do you have any strawman suggestions for a better scheme doing this?
@@ -226,13 +226,15 @@ private[spark] class Client( | |||
logInfo("Successfully submitted local resources and driver configuration to" + | |||
" driver pod.") | |||
// After submitting, adjust the service to only expose the Spark UI | |||
val serviceType = if (sparkConf.get(EXPOSE_KUBERNETES_DRIVER_SERVICE_UI_PORT)) "NodePort" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rename serviceType
to uiServiceType
I was thinking along these same lines. This change makes sense for the short term. |
Did the quick rename, good to merge when the build is green |
25a209b
into
apache-spark-on-k8s:k8s-support-alternate-incremental
Thanks for merging in this change. @foxish, @ash211 It occurred to me that we may want to consider hierarchical config options for services that may be formatted in json or yaml, much like k8s resources. Otherwise, the flat key=value options may become messy pretty soon.
|
* Optionally expose driver UI as a NodePort * Update the usage doc * Rename serviceType -> uiServiceType
* Optionally expose driver UI as a NodePort * Update the usage doc * Rename serviceType -> uiServiceType
…#131) * Optionally expose driver UI as a NodePort * Update the usage doc * Rename serviceType -> uiServiceType
What changes were proposed in this pull request?
Addresses #129 by optionally exposing the driver Web UI as NodePort.
How was this patch tested?
Tested again my k8s cluster. I was able to look at the Web UI using my browser.
Ran the integration test successfully: