Skip to content

Clarify supported version update paths in documentation#957

Open
fossedihelm wants to merge 1 commit into
kubevirt:mainfrom
fossedihelm:specify-supported-upgrade
Open

Clarify supported version update paths in documentation#957
fossedihelm wants to merge 1 commit into
kubevirt:mainfrom
fossedihelm:specify-supported-upgrade

Conversation

@fossedihelm
Copy link
Copy Markdown
Contributor

@fossedihelm fossedihelm commented Jan 16, 2026

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:

  • Minor version upgrades (e.g., from v1.6.3 to v1.7.0)
  • Patch version upgrades (e.g., from v1.6.2 to v1.6.3)
  • An example of what is NOT supported (e.g., from v1.5.2 to v1.7.0)

This makes it clearer for users to understand exactly which upgrade paths are supported when updating their KubeVirt installations.

Release note:

NONE

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Jan 16, 2026
@fossedihelm
Copy link
Copy Markdown
Contributor Author

fossedihelm commented Jan 16, 2026

/hold
The new sentences are true once kubevirt/kubevirt#16335 is merged

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 16, 2026
@fossedihelm fossedihelm mentioned this pull request Jan 16, 2026
Merged
8 tasks
dhiller
dhiller approved these changes Jan 21, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@dhiller dhiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

Thank you @fossedihelm !

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 21, 2026
@kubevirt-bot
Copy link
Copy Markdown
Contributor

kubevirt-bot commented Jan 21, 2026

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 21, 2026
xpivarc
xpivarc reviewed Feb 17, 2026
View reviewed changes
Comment thread docs/cluster_admin/updating_and_deletion.md Outdated
@kubevirt-bot
Copy link
Copy Markdown
Contributor

kubevirt-bot commented May 7, 2026

There has been no activity on this PR for 45 days.
To protect limited CI resources, it has been automatically labelled 'stale'.
This PR will automatically rot after an additional 14 days of inactivity, and will be closed shortly after that.

What you can do:

  • If the PR is waiting on you to respond to a question or feedback and/or update the PR, please do so.
  • You can mark the PR as fresh and remove the label with the following command: /remove-lifecycle stale
  • If this PR is safe to close now, please help the project by closing it with: /close
  • If you need attention on this PR from a reviewer, you can raise it on the agenda of the relevant SIG meeting or KubeVirt Community meeting, or ping the kubevirt-dev slack channel.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 7, 2026
@fossedihelm fossedihelm force-pushed the specify-supported-upgrade branch from ff53f74 to 68fb9db Compare May 13, 2026 09:34
@kubevirt-bot kubevirt-bot removed the lgtm Indicates that a PR is ready to be merged. label May 13, 2026
@kubevirt-bot
Copy link
Copy Markdown
Contributor

kubevirt-bot commented May 13, 2026

New changes are detected. LGTM label has been removed.

@fossedihelm
Copy link
Copy Markdown
Contributor Author

fossedihelm commented May 13, 2026

/remove-lifecycle stale
@dhiller @xpivarc can u take another look?
/unhold
kubevirt/kubevirt#16335 merged

@kubevirt-bot kubevirt-bot removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels May 13, 2026
aburdenthehand
aburdenthehand reviewed May 15, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@aburdenthehand aburdenthehand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, sorry I didn't see this sooner.
Content looks great but there's some formatting issues

Comment thread docs/cluster_admin/updating_and_deletion.md Outdated
`v0.17.0` release is not supported.

> 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:
Copy link
Copy Markdown
Member

@aburdenthehand aburdenthehand May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately this does not build properly on the preview: https://deploy-preview-957--kubevirt-user-guide.netlify.app/cluster_admin/updating_and_deletion/

We need a newline before the bulllet list

Comment thread docs/cluster_admin/updating_and_deletion.md Outdated
> 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 the latest patch version of one minor version to the latest patch version of the next minor version
> - For example: if latest 1.7 is v1.7.6 and latest 1.6 is v1.6.4
Copy link
Copy Markdown
Member

@aburdenthehand aburdenthehand May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each sub-point needs 4 spaces (or tab) to nest properly

@fossedihelm fossedihelm force-pushed the specify-supported-upgrade branch 5 times, most recently from 30ddce4 to 07bc81f Compare May 15, 2026 15:24
@fossedihelm
Clarify supported version update paths in documentation
e2e6c99 
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>
@fossedihelm fossedihelm force-pushed the specify-supported-upgrade branch from 07bc81f to e2e6c99 Compare May 15, 2026 15:25
@fossedihelm
Copy link
Copy Markdown
Contributor Author

fossedihelm commented May 15, 2026

Thank you @aburdenthehand
I fight a bit with the formatting but maybe I got it now :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aburdenthehand aburdenthehand aburdenthehand left review comments

@dhiller dhiller dhiller approved these changes

@victortoso victortoso Awaiting requested review from victortoso

+1 more reviewer

@xpivarc xpivarc xpivarc left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@dhiller dhiller

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/S

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@fossedihelm @kubevirt-bot @dhiller @aburdenthehand @xpivarc