kuberay
kuberay copied to clipboard
ray-project
[Discussion] KubeRay and Ray version compatibilities
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
Description
Following up on version compatibility metrics from last community meeting, I think we can follow following rules.
-
Community supports 2 KubeRay versions including bug fixes, testings and patch version releases. We only have two version including upcoming v0.2.0. Once v0.3.0 is released, we don't maintain v0.1-branch any more.
-
For each Kuberay version, it should support latest 3 Ray versions. for example, KubeRay v0.2.0 should support 1.9, 1.10 and 1.11. These three version should be fully tested.
This page documents the compatibility matrix of versions of Ray, KubeRay and Kubernetes. These combinations of versions are specifically tested in CI and supported by the Ray and KubeRay maintainers.
| KubeRay Version | Ray Version | Kubernetes Versions |
|---|---|---|
| v0.2.0 | 1.9, 1.10, 1.11 | 1.19, 1.20, 1.21 |
| v0.1.0 | 1.7, 1.8, 1.9 | 1.16, 1.17, 1.18 |
Note:
The KubeRay project only tests a given version of Ray and Kubernetes against the versions list in the table above. Combinations not listed are not tested, guaranteed to work, but they may work
WDYT? Any suggestions?
/cc @DmitriGekhtman @pcmoritz
@Jeffwan Thanks for sharing the compatibility matrix, can you please state:
- Reasons for supporting 3 versions?
- Can we please define what does fully tested mean?
This is reasonable. Given the current cadence of Ray releases, I think 3 is a good number. We can revisit it later.
Fully tested would mean some suite of end-to-end tests is run prior to release -- the details are probably better left to another discussion issue.
For the Ray release cycle, a good goal would be to test compatibility with both KubeRay releases at the time of the Ray release. That would add some forward compatibility for KubeRay.
An example of semantically matching the release versions to the upstream project (i.e. tagging kuberay at 1.11.0 for clarity): https://kops.sigs.k8s.io/welcome/releases/
@kevin85421 have we addressed this call out as part of kuberay ga last year?
@anyscalesam We have a doc for KubeRay / Ray compatibility. I may need to add more details about KubeRay / Kubernetes compatibility.
