docs: align Kubernetes support window#13216
Conversation
k8s-ci-robot
added
release-note-none
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yankay The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
There was a problem hiding this comment.
Pull request overview
Documentation update to align Kubespray’s published Kubernetes support/upgrade guidance with the currently maintained Kubernetes minor-version window reflected in *_checksums.
Changes:
- Update upgrade examples in
docs/operations/upgrades.mdto use Kubernetes v1.33/v1.34. - Clarify release maintenance policy around which Kubernetes minors are retained in
*_checksumsinRELEASE.md. - Raise README’s minimum supported Kubernetes version to v1.33.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/operations/upgrades.md | Refreshes upgrade command/output examples to newer Kubernetes versions. |
| RELEASE.md | Documents the supported/minor window policy for checksum variables during major releases. |
| README.md | Updates stated minimum Kubernetes version requirement. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - The cri-o version should be aligned with the respective kubernetes version (i.e. kube_version=1.20.x, crio_version=1.20) | ||
|
|
||
| ## Requirements | ||
|
|
||
| - **Minimum required version of Kubernetes is v1.30** | ||
| - **Minimum required version of Kubernetes is v1.33** |
There was a problem hiding this comment.
The "Container Runtime Notes" example still references very old Kubernetes/CRI-O versions ("kube_version=1.20.x, crio_version=1.20"), which now conflicts with the updated minimum Kubernetes version (v1.33) and the currently supported window. Please update this example to match the supported Kubernetes minor versions (and corresponding CRI-O major/minor) so readers don’t copy an unsupported pairing.
yankay
force-pushed
the
docs/kube-version-support-window
branch
from
b9e6128 to
1f0b647
Compare
Clarify that release maintenance keeps the default Kubernetes minor and two previous minors, and update docs examples to match the current supported window. Signed-off-by: Kay Yan <kay.yan@daocloud.io>
yankay
force-pushed
the
docs/kube-version-support-window
branch
from
1f0b647 to
2e35110
Compare
k8s-ci-robot
added
size/XS
| 1. An issue is proposing a new release with a changelog since the last release. Please see [a good sample issue](https://github.com/kubernetes-sigs/kubespray/issues/8325) | ||
| 1. At least one of the [approvers](OWNERS_ALIASES) must approve this release | ||
| 1. (Only for major releases) The `kube_version_min_required` variable is set to `n-1` | ||
| 1. (Only for major releases) The `kube_version_min_required` variable is set to `n-2` |
There was a problem hiding this comment.
I'm not entirely sure how version support is defined here, but if a version is included in the checksums, that implies it's supported, doesn’t it?
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Clarifies the Kubernetes support window used by the release process and aligns the README minimum Kubernetes version with the current checksum-backed minimum version.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
This is a documentation-only update to align the release guide and README with the versions currently present in
*_checksums.Does this PR introduce a user-facing change?: