You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/virt-about-upgrading-virt.adoc
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,20 +5,23 @@
5
5
[id="virt-about-upgrading-virt_{context}"]
6
6
= About upgrading {VirtProductName}
7
7
8
+
[id="how-upgrades-work_{context}"]
8
9
== How {VirtProductName} upgrades work
9
10
10
-
* You can upgrade to the next minor version of {VirtProductName} by using the
11
-
{product-title} web console to change the channel of your Operator subscription.
11
+
* 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.
12
12
13
-
* You can enable automatic _z-stream_ updates during {VirtProductName} installation.
13
+
* OLM provides z-stream and minor version updates for {VirtProductName}. Minor version updates become available when you upgrade {product-title} to the next minor version. You cannot upgrade {VirtProductName} to the next minor version without first upgrading {product-title}.
14
14
15
-
* Updates are delivered via the _Marketplace Operator_, which is deployed
16
-
during {product-title} installation. The Marketplace Operator makes
17
-
external Operators available to your cluster.
15
+
* {VirtProductName} subscriptions use a single update channel that is named *stable*. The *stable* channel ensures that your {VirtProductName} and {product-title} versions are compatible.
16
+
17
+
* If your subscription's approval strategy is set to *Automatic*, the upgrade process starts as soon as a new version of the Operator is available in the *stable* channel. It is highly recommended to use the *Automatic* approval strategy to maintain a supportable environment. Each minor version of {VirtProductName} is only supported if you run the corresponding {product-title} version. For example, you must run {VirtProductName} {VirtVersion} on {product-title} {VirtVersion}.
18
+
19
+
** Though it is possible to select the *Manual* approval strategy, this is not recommended because it risks the supportability and functionality of your cluster. With the *Manual* approval strategy, you must manually approve every pending update. If {product-title} and {VirtProductName} updates are out of sync, your cluster becomes unsupported.
18
20
19
21
* The amount of time an update takes to complete depends on your network
20
22
connection. Most automatic updates complete within fifteen minutes.
21
23
24
+
[id="how-upgrades-affect-cluster_{context}"]
22
25
== How {VirtProductName} upgrades affect your cluster
23
26
24
27
* Upgrading does not interrupt virtual machine workloads.
Copy file name to clipboardExpand all lines: modules/virt-installing-virt-operator.adoc
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,6 @@ You can install the {VirtProductName} Operator from the {product-title} web cons
14
14
15
15
.Procedure
16
16
17
-
. Open a browser window and log in to the {product-title} web console.
18
-
19
17
. From the *Administrator* perspective, click *Operators* -> *OperatorHub*.
20
18
21
19
. In the *Filter by keyword* field, type *{VirtProductName}*.
@@ -26,9 +24,7 @@ You can install the {VirtProductName} Operator from the {product-title} web cons
26
24
27
25
. On the *Install Operator* page:
28
26
29
-
.. Select *stable* from the list of available *Update Channel* options. This ensures that:
30
-
* You install the version of {VirtProductName} that is compatible with your {product-title} version.
31
-
* When you update {product-title}, {VirtProductName} automatically updates to the next minor version.
27
+
.. Select *stable* from the list of available *Update Channel* options. This ensures that you install the version of {VirtProductName} that is compatible with your {product-title} version.
32
28
33
29
.. For *Installed Namespace*, ensure that the *Operator recommended namespace* option is selected. This installs the Operator in the mandatory `openshift-cnv` namespace, which is automatically created if it does not exist.
34
30
+
@@ -37,7 +33,14 @@ You can install the {VirtProductName} Operator from the {product-title} web cons
37
33
Attempting to install the {VirtProductName} Operator in a namespace other than `openshift-cnv` causes the installation to fail.
38
34
====
39
35
40
-
.. For *Approval Strategy*, ensure that *Automatic*, which is the default value, is selected. {VirtProductName} automatically updates when a new z-stream release is available.
36
+
.. For *Approval Strategy*, it is highly recommended that you select *Automatic*, which is the default value, so that {VirtProductName} automatically updates when a new version is available in the *stable* update channel.
37
+
+
38
+
While it is possible to select the *Manual* approval strategy, this is inadvisable because of the high risk that it presents to the supportability and functionality of your cluster. Only select *Manual* if you fully understand these risks and cannot use *Automatic*.
39
+
+
40
+
[WARNING]
41
+
====
42
+
Because {VirtProductName} is only supported when used with the corresponding {product-title} version, missing {VirtProductName} updates can cause your cluster to become unsupported.
43
+
====
41
44
42
45
. Click *Install* to make the Operator available to the `openshift-cnv` namespace.
0 commit comments