|
Ran
|
Jobs
1
|
Files
151
|
Run time
1min
|
Badge
README BADGES
|
push
github
docs: list Kubernetes 1.33 to 1.35 as supported and say what was tested (#147) Every Valkey version in the supported-versions tables now lists Kubernetes 1.33, 1.34 and 1.35, and the user guide asks for 1.33 or later. 1.31 and 1.32 are no longer listed: this release was not tested on them. The v2.1.0 release candidate (69bc374) passed the in-cluster end-to-end suite: - Kubernetes v1.33.12 and v1.34.11 on kind, three nodes each: every Valkey version, 527 specs per cluster, no failures. - Kubernetes v1.35.6, four nodes: Valkey 7.2, 8.1 and 9.1, 325 specs, no failures. That cluster's registry carries no 8.0 or 9.0 image; the operator uses the same Kubernetes APIs whatever the Valkey version, so the 1.35 run stands for them as well. The line under each table says which combinations ran. The three copies of the table (README.md, docs/README.md and the operator overview) change together, each keeping its own column names and status style. (cherry picked from commit d07ff9a99)
7766 of 21918 relevant lines covered (35.43%)
0.4 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 2 |
74.19
|
-1.61% | cmd/helper/sync/file.go |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 36405697776.1 | 151 |
35.43
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|