This is an automated email from the ASF dual-hosted git repository.

dongjoon pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/spark-kubernetes-operator.git


The following commit(s) were added to refs/heads/main by this push:
     new e8e9124  [SPARK-54795] Suppress Hadoop warnings in History Server 
example
e8e9124 is described below

commit e8e912467725aa1d9d56a721c0a9edae9ca5f73a
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Mon Dec 22 09:30:15 2025 +0900

    [SPARK-54795] Suppress Hadoop warnings in History Server example
    
    ### What changes were proposed in this pull request?
    
    This PR aims to suppress Hadoop warnings in History Server example.
    
    ### Why are the changes needed?
    
    Since we don't use `KerberosConfDriverFeatureStep` in our example, we can 
skip this step to avoid irrelevant Hadoop warnings on Java 25 like the other 
examples.
    
    ### Does this PR introduce _any_ user-facing change?
    
    No.
    
    ### How was this patch tested?
    
    Manual review.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    No.
    
    Closes #442 from dongjoon-hyun/SPARK-54795.
    
    Authored-by: Dongjoon Hyun <[email protected]>
    Signed-off-by: Dongjoon Hyun <[email protected]>
---
 examples/spark-history-server.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/examples/spark-history-server.yaml 
b/examples/spark-history-server.yaml
index 2754198..f56e28b 100644
--- a/examples/spark-history-server.yaml
+++ b/examples/spark-history-server.yaml
@@ -35,6 +35,7 @@ spec:
     spark.hadoop.fs.s3a.path.style.access: "true"
     spark.hadoop.fs.s3a.access.key: "test"
     spark.hadoop.fs.s3a.secret.key: "test"
+    spark.kubernetes.driver.pod.excludedFeatureSteps: 
"org.apache.spark.deploy.k8s.features.KerberosConfDriverFeatureStep"
   runtimeVersions:
     sparkVersion: "4.1.0"
   applicationTolerations:


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to