GitHub user gurvindersingh opened a pull request:
https://github.com/apache/spark/pull/13950
[SPARK-15487] [Web UI] Spark Master UI to reverse proxy Application and
Workers UI
## What changes were proposed in this pull request?
This pull request adds the functionality to enable accessing worker and
application UI through master UI itself. Thus helps in accessing SparkUI when
running spark cluster in closed networks e.g. Kubernetes. Cluster admin needs
to expose only spark master UI and rest of the UIs can be in the private
network, master UI will reverse proxy the connection request to corresponding
resource. It adds the path for workers/application UIs as
WorkerUI: <http/https>://master-publicIP:<port>/target/workerID/
ApplicationUI: <http/https>://master-publicIP:<port>/target/appID/
This makes it easy for users to easily protect the Spark master cluster
access by putting some reverse proxy e.g. https://github.com/bitly/oauth2_proxy
## How was this patch tested?
The functionality has been tested manually and there is a unit test too for
testing access to worker UI with reverse proxy address.
@pwendell @bomeng @BryanCutler can you please review it, thanks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gurvindersingh/spark rproxy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13950.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13950
----
commit 19c8dc6fdc2d1de11cedb7e706a7ce1c04f2f06a
Author: Gurvinder Singh <[email protected]>
Date: 2016-05-26T21:14:05Z
added support for reverse proxying request to workers and application UI.
This helps in accessing SparkUI when running spark cluster in closed networks.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
