openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Added <shortdesc> to Updating sections

Browse Source
This commit is contained in:
vathakur
2025-11-20 13:54:55 +05:30
committed by openshift-cherrypick-robot
parent ccac00fec5
commit 8281332ae9
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
modules/virt-about-upgrading-virt.adoc
View File

@@ -3,6 +3,7 @@
// * virt/updating/upgrading-virt.adoc
:_mod-docs-content-type: CONCEPT
[id="virt-about-upgrading-virt_{context}"]
= About updating {VirtProductName}
@@ -32,6 +33,8 @@ Each minor version of {VirtProductName} is supported only if you run the corresp
[id="what-to-expect_{context}"]
== What to expect
You can anticipate update behavior in {VirtProductName}, including duration, automation, and data preservation.
* The amount of time an update takes to complete depends on your network
connection. Most automatic updates complete within fifteen minutes.
@@ -59,6 +62,8 @@ endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
[id="how-updates-work_{context}"]
== How updates work
Learn how the {VirtProductName} Operator is updated through the Operator Lifecycle Manager (OLM) and how update channels and approval strategies affect upgrade behavior.
* 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}.