Clarify supported version update paths in documentation#957
Open
fossedihelm wants to merge 1 commit intokubevirt:mainfrom
Open
Clarify supported version update paths in documentation#957fossedihelm wants to merge 1 commit intokubevirt:mainfrom
fossedihelm wants to merge 1 commit intokubevirt:mainfrom
Conversation
Expanded the update support note to include specific examples of supported upgrade paths (minor version upgrades and patch version upgrades) with concrete version numbers, making it clearer for users what update scenarios are supported. Signed-off-by: fossedihelm <ffossemo@redhat.com>
kubevirt-bot
added
the
dco-signoff: yes
Contributor
Author
|
/hold |
kubevirt-bot
added
the
do-not-merge/hold
dhiller
approved these changes
Jan 21, 2026
Contributor
dhiller
left a comment
dhiller
left a comment
There was a problem hiding this comment.
/approve
Thank you @fossedihelm !
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhiller 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 |
kubevirt-bot
added
the
approved
xpivarc
reviewed
Feb 17, 2026
|
|
||
| > Note: Updating is only supported from N-1 to N release. | ||
| > Note: Updating is only supported from N-1 to N release in the following form: | ||
| > - Upgrading from one minor version to the next (for example, from v1.6.3 to v1.7.0). |
Member
There was a problem hiding this comment.
Now here we should also clarify if v1.6.2 -> 1.7.0 is supported or not.
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
4 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.
This PR clarifies the supported version update paths in the KubeVirt documentation by expanding the upgrade support note with specific examples.
The previous note only stated "Updating is only supported from N-1 to N release" which was ambiguous. This update provides concrete examples showing:
This makes it clearer for users to understand exactly which upgrade paths are supported when updating their KubeVirt installations.
Release note: