[SPARK-44119][K8S][DOCS] Drop K8s v1.25 and lower version support#43069
Closed
dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-44119][K8S][DOCS] Drop K8s v1.25 and lower version support#43069dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
dongjoon-hyun wants to merge 1 commit intoapache:masterfrom
Conversation
Member
Author
|
Could you review this doc-only PR, @LuciferYang ? |
Member
Author
|
Thank you so much! |
Member
Author
|
Merged to master for Apache Spark 4.0.0. |
dongjoon-hyun
added a commit
that referenced
this pull request
Apr 22, 2024
### What changes were proposed in this pull request? This PR aims to update K8s docs to recommend K8s v1.27+ for Apache Spark 4.0.0. This is a kind of follow-up of the following previous PR because Apache Spark 4.0.0 schedule is delayed slightly. - #43069 ### Why are the changes needed? **1. K8s community starts to release v1.30.0 from 2024-04-17.** - https://kubernetes.io/releases/#release-v1-30 **2. Default K8s Version in Public Cloud environments** The default K8s versions of public cloud providers are already K8s 1.27+. - EKS: v1.29 (Default) - GKE: v1.29 (Rapid), v1.28 (Regular), v1.27 (Stable) - AKS: v1.27 **3. End Of Support** In addition, K8s 1.26 is going to reach EOL when Apache Spark 4.0.0 arrives because K8s 1.26 is also going to reach EOL on June. | K8s | AKS | GKE | EKS | | ---- | ------- | ------- | ------- | | 1.26 | 2024-03 | 2024-06 | 2024-06 | - [AKS EOL Schedule](https://docs.microsoft.com/en-us/azure/aks/supported-kubernetes-versions?tabs=azure-cli#aks-kubernetes-release-calendar) - [GKE EOL Schedule](https://cloud.google.com/kubernetes-engine/docs/release-schedule) - [EKS EOL Schedule](https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html#kubernetes-release-calendar) ### Does this PR introduce _any_ user-facing change? - No, this is a documentation-only change about K8s versions. - Apache Spark K8s Integration Test is currently using K8s v1.30.0 on Minikube already. ### How was this patch tested? Manual review. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #46168 from dongjoon-hyun/SPARK-47942. Authored-by: Dongjoon Hyun <dhyun@apple.com> Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR aims to update K8s doc to recommend K8s 1.26+ for Apache Spark 4.0.0.
Why are the changes needed?
1. Default K8s Version in Public Cloud environments
The default K8s versions of public cloud providers are already K8s 1.27+.
2. End Of Support
In addition, K8s 1.25 and olders are going to reach EOL when Apache Spark 4.0.0 arrives on June 2024. K8s 1.26 is also going to reach EOL on June.
Does this PR introduce any user-facing change?
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.