Stavros Kontopoulos created SPARK-26973:
-------------------------------------------
Summary: Kubernetes version support strategy on test nodes and for
the backend
Key: SPARK-26973
URL: https://issues.apache.org/jira/browse/SPARK-26973
Project: Spark
Issue Type: Test
Components: Kubernetes
Affects Versions: 3.0.0
Reporter: Stavros Kontopoulos
Kubernetes has a policy for supporting three minor releases and the current are
defined here:
[https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md.|https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md].]
Moving from release 1.x to 1.(x+1) happens roughly every 100
days:[https://gravitational.com/blog/kubernetes-release-cycle.]
This has an effect on dependencies upgrade at the Spark on K8s backend and the
version of Minikube required to be supported for testing. One other issue is
what the users actually want at the given time of a release. Some popular
vendors like EKS([https://aws.amazon.com/eks/faqs/] have their own roadmap for
releases.
Follow the comments a recent discussion on the topic:
[https://github.com/apache/spark/pull/23814.]
Clearly we need a strategy for this.
A couple of options for the current state of things:
a) Support only the last two version, but that leaves out a version that still
receives patches.
b) Support only the latest, which makes testing easier, but leaves out other
currently maintained version.
A good strategy will optimize the following:
1) percentage of users satisfied at release time.
2) how long it takes to support the latest K8s version
3) testing requirements eg. minikube versions used
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
