docs: add Kubernetes compatibility matrix, update stale max-kube version - #455
Open
yashrajshuklaaa wants to merge 2 commits into
Open
docs: add Kubernetes compatibility matrix, update stale max-kube version#455yashrajshuklaaa wants to merge 2 commits into
yashrajshuklaaa wants to merge 2 commits into
Conversation
Addresses kagent-dev/kagent#2268 Signed-off-by: Yashraj Shukla <shuklayashraj68@gmail.com>
…ion form) Signed-off-by: Yashraj Shukla <shuklayashraj68@gmail.com>
artberger
reviewed
Aug 14, 2026
artberger
left a comment
artberger
left a comment
Collaborator
There was a problem hiding this comment.
Thank you for this PR. I left some comments/questions.
Comment on lines
+15
to
+16
| | v0.7.11 and later (including main) | 1.35 | Supported | | ||
| | v0.6.16 to v0.7.10 | 1.34 | Supported | |
Collaborator
There was a problem hiding this comment.
What does Supported mean? I am not sure that we support any old versions of kagent except the latest (v0.9)
|
|
||
| ## Support policy | ||
|
|
||
| kagent tests and supports one Kubernetes minor version per release: whatever `KIND_IMAGE_VERSION` was pinned to when that release was cut. We want to move to an N-2 policy (current version plus the two before it) once CI actually runs a version matrix instead of a single pinned version. |
Collaborator
There was a problem hiding this comment.
Typically avoid 1st-person/"we".
We want to move to an N-2 policy
When was this decided? I did not see it in the issue, for example. Was it at a community meeting?
Comment on lines
+2
to
+3
| title: Kubernetes Compatibility | ||
| linkTitle: Kubernetes Compatibility |
Collaborator
There was a problem hiding this comment.
We might want to call this page just "Version support" and rename the file versions.md in case we want to discuss more than just Kubernetes versions down the road.
For example, related projects like agentgateway.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Kubernetes version compatibility page under Resources, and fixes a stale value in the max-kube version snippet.
Addresses kagent-dev/kagent#2268
What this does
Adds docs-site/content/kagent/resources/kubernetes-compatibility.md, a new Resources page listing which Kubernetes version each kagent release is tested against, plus a stated support policy.
Updates docs-site/assets/versions/max-kube.md from 1.31 to 1.35. This snippet existed already but was stale and not referenced from any page, so it was silently out of date.
Where the numbers come from
The tested Kubernetes version is KIND_IMAGE_VERSION in the kagent repo's Makefile, which pins the kindest/node image used in CI. History pulled from git log on that Makefile:
v0.6.16 to v0.7.10: 1.34
v0.7.11 onward (current main): 1.35
CI currently tests one Kubernetes minor version per release, not a matrix. The page states this directly rather than implying broader coverage than what's actually tested. It also notes client-go's version skew policy as a rough guide for untested versions, without claiming compatibility kagent doesn't actually verify.
Follow-up, not part of this PR
Moving to an N-2 support policy (testing the current version plus two prior) would need CI to run a version matrix instead of a single pinned KIND_IMAGE_VERSION. That's a change to the kagent repo's CI, not this docs repo, so it's left as a follow-up rather than bundled here.
Testing
Built locally with hugo160 (extended, per DEVELOPMENT.md). Confirmed the reuse shortcode resolves correctly, the table renders, and the page appears in the Resources nav at weight 4, between Tools Ecosystem and FAQs.