Skip to content

CNV- 58675: Added <shortdesc> to Updating sections #102801

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

CNV- 58675: Added <shortdesc> to Updating sections #102801

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions modules/virt-about-upgrading-virt.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@
// * virt/updating/upgrading-virt.adoc

:_mod-docs-content-type: CONCEPT
include::_attributes/common-attributes.adoc[]
[id="virt-about-upgrading-virt_{context}"]
= About updating {VirtProductName}

Expand Down Expand Up @@ -32,6 +33,9 @@ Each minor version of {VirtProductName} is supported only if you run the corresp
[id="what-to-expect_{context}"]
== What to expect

[role="_abstract"]
This topic helps you understand what happens during an {VirtProductName} update, including expected completion time and preservation of data.
Copy link
Contributor

@jherrman jherrman Nov 21, 2025

Choose a reason for hiding this comment

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

Suggested change
This topic helps you understand what happens during an {VirtProductName} update, including expected completion time and preservation of data.
For details on what happens during an {VirtProductName} update, including expected completion time and preservation of data, see below.


* The amount of time an update takes to complete depends on your network
connection. Most automatic updates complete within fifteen minutes.

Expand Down Expand Up @@ -59,6 +63,9 @@ endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
[id="how-updates-work_{context}"]
== How updates work

[role="_abstract"]
This topic helps you understand how the {VirtProductName} Operator is managed and updated using the Operator Lifecycle Manager (OLM).
Copy link
Contributor

@jherrman jherrman Nov 21, 2025

Choose a reason for hiding this comment

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

Suggested change
This topic helps you understand how the {VirtProductName} Operator is managed and updated using the Operator Lifecycle Manager (OLM).
For details on how the {VirtProductName} Operator is managed and updated by using the Operator Lifecycle Manager (OLM), see below.


* Operator Lifecycle Manager (OLM) manages the lifecycle of the {VirtProductName} Operator. The Marketplace Operator, which is deployed during {product-title} installation, makes external Operators available to your cluster.

* OLM provides z-stream and minor version updates for {VirtProductName}. Minor version updates become available when you update {product-title} to the next minor version. You cannot update {VirtProductName} to the next minor version without first updating {product-title}.