Skip to content

[SPARK-56834][K8S] Use Java 25-jre instead of 21-jre image in K8s Dockerfile#55829

Closed
dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-56834
Closed

[SPARK-56834][K8S] Use Java 25-jre instead of 21-jre image in K8s Dockerfile#55829
dongjoon-hyun wants to merge 1 commit into
apache:masterfrom
dongjoon-hyun:SPARK-56834

Conversation

@dongjoon-hyun
Copy link
Copy Markdown
Member

@dongjoon-hyun dongjoon-hyun commented May 12, 2026

What changes were proposed in this pull request?

This PR aims to use Java 25 image in the Spark K8s Dockerfile.

Why are the changes needed?

As a part of SPARK-51167 Build and Run Spark on Java 25, this PR uses the latest LTS Java release as the default JVM docker base image in Apache Spark 4.2.0.

Does this PR introduce any user-facing change?

  • Yes because the default Java version is changed.
  • However, a user still change this back via -b java_image_tag=17 and the Apache Spark 4.2.0 provides the same capability for Java 17/21/25.

How was this patch tested?

Manual review.

Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

@dongjoon-hyun dongjoon-hyun changed the title [SPARK-56834] Use Java 25-jre instead of 21-jre image in K8s Dockerfile [SPARK-56834][K8S] Use Java 25-jre instead of 21-jre image in K8s Dockerfile May 12, 2026
@dongjoon-hyun
Copy link
Copy Markdown
Member Author

Thank you, @LuciferYang .

@dongjoon-hyun
Copy link
Copy Markdown
Member Author

Thank you, @yaooqinn !

dongjoon-hyun added a commit that referenced this pull request May 12, 2026
… Dockerfile

### What changes were proposed in this pull request?

This PR aims to use Java 25 image in the Spark K8s Dockerfile.

### Why are the changes needed?

As a part of [SPARK-51167 Build and Run Spark on Java 25](https://issues.apache.org/jira/browse/SPARK-51167), this PR uses the latest LTS Java release as the default JVM docker base image in Apache Spark 4.2.0.
- #55798
- #55827

### Does this PR introduce _any_ user-facing change?

- Yes because the default Java version is changed.
- However, a user still change this back via `-b java_image_tag=17` and the Apache Spark 4.2.0 provides the same capability for Java 17/21/25.

### How was this patch tested?

Manual review.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

Closes #55829 from dongjoon-hyun/SPARK-56834.

Authored-by: Dongjoon Hyun <dongjoon@apache.org>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
(cherry picked from commit 7a01891)
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
dongjoon-hyun added a commit that referenced this pull request May 12, 2026
… Dockerfile

### What changes were proposed in this pull request?

This PR aims to use Java 25 image in the Spark K8s Dockerfile.

### Why are the changes needed?

As a part of [SPARK-51167 Build and Run Spark on Java 25](https://issues.apache.org/jira/browse/SPARK-51167), this PR uses the latest LTS Java release as the default JVM docker base image in Apache Spark 4.2.0.
- #55798
- #55827

### Does this PR introduce _any_ user-facing change?

- Yes because the default Java version is changed.
- However, a user still change this back via `-b java_image_tag=17` and the Apache Spark 4.2.0 provides the same capability for Java 17/21/25.

### How was this patch tested?

Manual review.

### Was this patch authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.7)

Closes #55829 from dongjoon-hyun/SPARK-56834.

Authored-by: Dongjoon Hyun <dongjoon@apache.org>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
(cherry picked from commit 7a01891)
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
@dongjoon-hyun
Copy link
Copy Markdown
Member Author

Merged to master/4.x/4.2.

@dongjoon-hyun dongjoon-hyun deleted the SPARK-56834 branch May 12, 2026 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants