From ff53f74d636757e5a907fe2e7116393a9ce80d5e Mon Sep 17 00:00:00 2001 From: fossedihelm Date: Fri, 16 Jan 2026 10:47:36 +0100 Subject: [PATCH] Clarify supported version update paths in documentation 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 --- docs/cluster_admin/updating_and_deletion.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/cluster_admin/updating_and_deletion.md b/docs/cluster_admin/updating_and_deletion.md index 176d173ee..c1bc8225d 100644 --- a/docs/cluster_admin/updating_and_deletion.md +++ b/docs/cluster_admin/updating_and_deletion.md @@ -6,7 +6,11 @@ Zero downtime rolling updates are supported starting with release `v0.17.0` onward. Updating from any release prior to the KubeVirt `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: +> - Upgrading from one minor version to the next (for example, from v1.6.3 to v1.7.0). +> - Upgrading to a later patch version (for example, from v1.6.2 to v1.6.3). +> +> Not supported example: from v1.5.2 to v1.7.0 Updates are triggered one of two ways.