Skip to content

Commit 3dd441a

Browse files
committed
chore: update readme
1 parent 7499719 commit 3dd441a

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

Readme.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ The proxy is non-intrusive and independent of any specific version of Spark Hist
2222
2323
## Installation
2424

25-
To deploy the spark web proxy, refer to helm chart [README](helm/spark-web-proxy/README.md) for customization options and installation guidelines.
25+
To deploy the Spark Web Proxy, refer to helm chart [README](helm/spark-web-proxy/README.md) for customization options and installation guidelines.
2626

2727
The web proxy can also be deployed as a sidecar container alongside your existing Spark History Server. Ensure to set the property `configuration.spark.service` to `localhost`.
2828

29-
In both cases, you need to use the spark web proxy ingress instead of your spark history ingress.
29+
In both cases, you need to use the Spark Web Proxy ingress instead of your spark history ingress.
3030

3131
## Spark History and spark jobs Configuration
3232

@@ -101,4 +101,6 @@ conf.set("spark.ui.port", find_available_port())
101101

102102
## Authentication
103103

104-
[Spark Authentication Filter](https://github.com/OKDP/okdp-spark-auth-filter) can be applied to both Spark History Server and Spark Jobs to enable user authentication and authorization.
104+
The Spark Web Proxy is independent of any specific authentication mechanism. It simply forwards credentials and headers to the running Spark instances without modifying or enforcing authentication itself.
105+
106+
This allows to use the [Spark Authentication Filter](https://github.com/OKDP/okdp-spark-auth-filter) or any other authentication solution to secure both the Spark History Server and Spark Jobs to ensure user authentication and authorization.

0 commit comments

Comments
 (0)