dongjoon-hyun opened a new pull request, #781: URL: https://github.com/apache/spark-kubernetes-operator/pull/781
### What changes were proposed in this pull request? This PR aims to use `7077` for the `spark` named container port in the master StatefulSet of `SparkClusterResourceSpec`, instead of `7070`. ### Why are the changes needed? The `spark` named container port declaration was inconsistent with the actual master RPC port. The Spark standalone master listens on `7077` (the default of `SPARK_MASTER_PORT`), and all other references agree on `7077`: - The master Service exposes port `7077` with `targetPort: spark` (a named port reference). - Workers connect via `spark://<name>-master-svc:7077`. Currently, this mismatch is harmless because the master Service is headless (`ClusterIP: None`), so workers resolve the pod IP via DNS and connect directly to `7077` without any Service port translation, and `containerPort` itself is a non-enforcing declaration. However, the stale value would surface as a real failure if: 1. A user overrides `masterSpec.serviceSpec` with a non-headless Service type, where `targetPort: spark` would resolve to `7070` and break connections. 2. Any Endpoints/EndpointSlice consumer (e.g., Prometheus service discovery, service mesh) reads the resolved port. 3. A NetworkPolicy referencing the named port is added on the master side. ### Does this PR introduce _any_ user-facing change? No, for the default headless master Service. The generated master pod spec now declares the correct port, which only affects configurations that resolve the `spark` named port. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Claude Fable 5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
