Repository navigation
docs: bump kgateway to v2.3.11 to install on Kubernetes 1.37 - #965
Conversation
Signed-off-by: Miraj Abeysekara <miraj@wso2.com>
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update installation version references docs/getting-started/try-it-out/on-k3d-locally.mdx, docs/getting-started/try-it-out/on-your-environment.mdx, docs/platform-engineer-guide/air-gapped-installation.mdx |
The getting-started guides use v2.3.11 in kgateway chart install commands. The air-gapped guide uses v2.3.11 for image references, chart downloads, and local archive installation commands. |
Priority:
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Other · Severity of issue fixed: Medium
Suggested reviewers: nomadxd, akila-i
Merge Risk: 
Minimal · up to c235b
-
The guides consistently select kgateway v2.3.11. No actionable installation regression was established, although compatibility with Kubernetes 1.37 remains unverified.
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Title check
-
Explanation
The title states the main change: bumping kgateway from v2.3.1 to v2.3.11 in the docs so installation works on Kubernetes 1.37. The raw summary confirms the version bump across the getting-started and air-gapped docs, and the description gives the same reason, so the title matches the changeset.
Full details: Description check
-
Explanation
The description covers the Purpose section, which explains the version bump from v2.3.1 to v2.3.11 across the current, v1.3.x and v1.2.x guides and the CEL cost failure on Kubernetes 1.37. It also has the Related Issues section, which links openchoreo/openchoreo#5203. The checklist is copied from the template but left unchecked, so the preview, build and link checks are not reported as done.
Full details: Out of Scope Changes check
-
Explanation
The reviewed changes update kgateway versions in installation, local k3d, and air-gapped documentation. These changes directly support the linked issue's kgateway installation fix and do not show unrelated product or documentation changes. Excluded versioned files were not used as evidence of additional changes.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)
-
Full details: Linked Issues check
-
Explanation
Issue
#5203reports that kgateway v2.3.1 CRDs fail Kubernetes CEL cost validation and suggests kgateway v2.4.x, specifically v2.4.7. This PR changes the documented version to v2.3.11. The available change summary does not establish that v2.3.11 removes the reported validation failure. The PR therefore does not demonstrate compliance with the linked issue's required fix.Resolution
Update the affected installation commands to a kgateway version that resolves the Kubernetes 1.37 CRD validation failure, consistent with issue
#5203's v2.4.x recommendation, and verify the affected guides use that version.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
Purpose
Bump kgateway from v2.3.1 to v2.3.11 in the install guides (current, v1.3.x and v1.2.x). The v2.3.1 CRDs are rejected on Kubernetes 1.37 (CEL rule cost exceeds budget).
Related Issues
Fixes openchoreo/openchoreo#5203
Checklist
sidebars.tsif adding a new documentation pagenpm run startto preview the changes locallynpm run buildto ensure the build passes without errors