Publish a shared Kubernetes version support matrix
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
Create a shared definition of what Kubeflow supports. The testing repo becomes a source of truth for this configuration.
The divergence can be plainly observed from the support that exists at the time this issue is created.
| Repo | Matrix |
|---|---|
| trainer | 1.32.3, 1.33.1, 1.34.0, 1.35.0, 1.36.1, 1.37.0 |
| sdk | 1.32.3, 1.33.1, 1.34.0, 1.35.0 |
| spark-operator | v1.32.11, v1.33.7, v1.34.3, v1.35.0 |
| pipelines | v1.33.12, v1.36.1 |
| hub | v1.33.7, v1.34.3 |
| notebooks | v1.35.0 only |
Also standardize on the kind version for cross-project and end-to-end reproducibility.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing Kubernetes version configuration in the testing repository and comparing it with the trainer, sdk, spark-operator, pipelines, hub, and notebooks matrices listed here. Define the shared support matrix in testing, standardize on kind versions, and verify that the resulting definition supports cross-project and end-to-end reproducibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100