docs: add 26.2 to the Kubernetes compatibility matrix#1811
Conversation
26.2.x core with the 26.2.x chart/operator supports Kubernetes 1.33.x-1.36.x per engineering. Following the existing pattern, the new core block also lists the 26.1.x chart, and the 26.1.x core block gains a 26.2.x chart row (the chart supports its core version plus or minus one minor version).
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Feediver1
left a comment
Feediver1
left a comment
There was a problem hiding this comment.
PR Review: docs: add 26.2 to the Kubernetes compatibility matrix (#1811)
Files reviewed: 1 .adoc file (modules/upgrade/pages/k-compatibility.adoc)
Overall assessment: Clean, convention-faithful matrix update with no structural or consistency issues. The one unverifiable data point (the 1.36 upper bound) is already honestly flagged for SME confirmation in the PR body, and a source check corroborates the lower bound.
Verification performed
- Rowspans are correct:
.2+|26.2.xcovers exactly 2 rows; the widened.3+|26.1.xcovers exactly 3 (including the pre-existing 25.3-chart row); 5 cells per row against the 6-column header. - The "older component's range" convention claim is real: the distinguishing pre-existing row (26.1 core + 25.3 chart → 1.30–1.33, the 25.3 range) proves the convention, and all three new cross-version rows follow it correctly.
- ±1-minor policy: 26.1 core listing charts 26.2/26.1/25.3 matches the page's stated policy; 26.2 core correctly omits a nonexistent 26.3 chart.
- Source corroboration for the K8s range: operator CI on
main(the 26.2 line) tests on kindv1.33.7— consistent with 1.33 as the floor. The 1.36 ceiling isn't evidenced in CI (which pins one version) and rests on the SME statement, exactly as the PR body discloses — the requested David/Rafal confirmation remains the right gate before merge. - The
{fn-k8s-compatibility}footnote resolves, and thed|footnote-rendering comment stays adjacent to the first Kubernetes cell. - No stale hardcoded K8s ranges elsewhere: repo-wide grep found no other page asserting a K8s version range, consistent with #1681/#1787 deferring to this matrix.
Suggestions (non-blocking)
- The versioning-policy prose example still reads "Redpanda Operator version 25.3.1 supports Redpanda core versions 26.1.x, 25.3.x, and 25.2.x." Accurate but aging — consider refreshing to a 26.2 example while touching this page.
- Merge-order note: #1681 and #1787 both link to this matrix instead of hardcoding versions — ideally they land after or alongside this PR so the table they point at actually contains 26.2.
- No Jira key on the PR — if a DOC ticket exists for the 26.2 compat matrix, worth linking for traceability.
What works well
- The PR body is a model of verifiable claims: it names the evidence source for the range, discloses which part needs SME confirmation and from whom, and explains the cross-version range convention it followed — all of which checked out against the file and the operator repo.
- Minimal diff: rows added without disturbing any existing row.
- Pre-GA targeting of
betais correct, and the page's beta-versions NOTE already covers the current operator state (26.2 still-betaon Docker Hub).
🤖 Generated with Claude Code
2 participants
Adds the 26.2 rows to the compatibility matrix ahead of GA (July 28):
26.2.xcore block: 26.2.x chart/operator supports Kubernetes 1.33.x - 1.36.x (per engineering; see the discussion on the Pipeline CRD PR where testing on 1.28 produced a false blocker), plus a 26.1.x chart row.26.1.xcore block gains a 26.2.x chart row, following the plus-or-minus-one-minor support policy and the pattern used when 26.1 was added (the 25.3 block lists the 26.1 chart).The Kubernetes ranges on cross-version rows follow the existing convention in the table (the row keeps the older component's tested range).
Reviewer check requested: please confirm the 1.33.x - 1.36.x range with the K8s team (David/Rafal) before merge; the source is David's statement that operator 26.2.x will support 1.33-1.36.
Related: #1681 and #1787 now reference this matrix instead of hardcoding technical-floor versions (1.28/1.31).
Preview pages