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/understanding-update-channels.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Red Hat monitors newly released versions and update paths associated with those
75
75
76
76
If Red Hat removes update recommendations from any supported release, a superseding update recommendation will be provided to a future version that corrects the regression. There may however be a delay while the defect is corrected, tested, and promoted to your selected channel.
77
77
78
-
Beginning in {product-title} 4.10, when update risks are confirmed, they are declared as Conditional Update risks for the relevant updates. Each known risk may apply to all clusters or only clusters matching certain conditions. Some examples include having the `Platform` set to `None` or the CNI provider set to `OpenShiftSDN`. The Cluster Version Operator (CVO) continually evaluates known risks against the current cluster state. If no risks match, the update is recommended. If the risk matches, those updates are supported but not recommended, and a reference link is provided. The reference link helps the cluster admin decide if they would like to accept the risk and update anyway.
78
+
Beginning in {product-title} 4.10, when update risks are confirmed, they are declared as Conditional Update risks for the relevant updates. Each known risk may apply to all clusters or only clusters matching certain conditions. Some examples include having the `Platform` set to `None` or the CNI provider set to `OpenShiftSDN`. The Cluster Version Operator (CVO) continually evaluates known risks against the current cluster state. If no risks match, the update is recommended. If the risk matches, those update paths are labeled as _updates with known issues_, and a reference link to the known issues is provided. The reference link helps the cluster admin decide if they want to accept the risk and continue to update their cluster.
79
79
80
80
When Red Hat chooses to declare Conditional Update risks, that action is taken in all relevant channels simultaneously. Declaration of a Conditional Update risk may happen either before or after the update has been promoted to supported channels.
Copy file name to clipboardExpand all lines: modules/update-availability-faq.adoc
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,18 +35,16 @@ The primary purpose of the `eus` channel is to serve as a convenience for cluste
35
35
* A release that is available on the `fast` channel always becomes available on the `stable` channel after this delay.
36
36
37
37
[id="supported-updates_{context}"]
38
-
*What does it mean if an update is supported but not recommended?*
38
+
*What does it mean if an update has known issues?*
39
39
40
-
* Red Hat continuously evaluates data from multiple sources to determine whether updates from one version to another lead to issues.
41
-
If an issue is identified, an update path may no longer be recommended to users.
42
-
However, even if the update path is not recommended, customers are still supported if they perform the update.
40
+
* Red{nbsp}Hat continuously evaluates data from multiple sources to determine whether updates from one version to another have any declared issues. Identified issues are typically documented in the version's release notes.
41
+
Even if the update path has known issues, customers are still supported if they perform the update.
43
42
44
43
* Red Hat does not block users from updating to a certain version.
45
44
Red Hat may declare conditional update risks, which may or may not apply to a particular cluster.
46
45
47
46
** Declared risks provide cluster administrators more context about a supported update.
48
47
Cluster administrators can still accept the risk and update to that particular target version.
49
-
This update is always supported despite not being recommended in the context of the conditional risk.
50
48
51
49
[id="removed-recommendation_{context}"]
52
50
*What if I see that an update to a particular release is no longer recommended?*
The additional `--include-not-recommended` parameter includes updates that are available but not recommended due to a known risk that applies to the cluster.
40
+
The additional `--include-not-recommended` parameter includes updates that are available with known issues that apply to the cluster.
41
41
====
42
42
+
43
43
.Example output
44
44
[source,terminal]
45
45
----
46
-
Cluster version is 4.10.22
46
+
Cluster version is 4.13.40
47
47
48
48
Upstream is unset, so the cluster will use an appropriate default.
Message: Nodes with substantial numbers of containers and CPU contention may not reconcile machine configuration https://bugzilla.redhat.com/show_bug.cgi?id=2111817#c22
Message: Exposure to AzureRegistryImageMigrationUserProvisioned is unknown due to an evaluation failure: client-side throttling: only 18.061µs has elapsed since the last match call completed for this cluster condition backend; this cached cluster condition request has been queued for later execution
68
+
In Azure clusters with the user-provisioned registry storage, the in-cluster image registry component may struggle to complete the cluster update. https://issues.redhat.com/browse/IR-468
69
+
70
+
Incoming HTTP requests to services exposed by Routes may fail while routers reload their configuration, especially when made with Apache HTTPClient versions before 5.0. The problem is more likely to occur in clusters with higher number of Routes and corresponding endpoints. https://issues.redhat.com/browse/NE-1689
Message: Exposure to AzureRegistryImageMigrationUserProvisioned is unknown due to an evaluation failure: client-side throttling: only 33.991µs has elapsed since the last match call completed for this cluster condition backend; this cached cluster condition request has been queued for later execution
76
+
In Azure clusters with the user-provisioned registry storage, the in-cluster image registry component may struggle to complete the cluster update. https://issues.redhat.com/browse/IR-468
77
+
78
+
Incoming HTTP requests to services exposed by Routes may fail while routers reload their configuration, especially when made with Apache HTTPClient versions before 5.0. The problem is more likely to occur in clusters with higher number of Routes and corresponding endpoints. https://issues.redhat.com/browse/NE-1689
66
79
----
67
80
+
68
81
The `oc adm upgrade` command queries the `ClusterVersion` resource for information about available updates and presents it in a human-readable format.
<.> `<version>` is the supported but not recommended update version that you obtained from the output of the previous command.
27
+
<.> `<version>` is the update version that you obtained from the output of the previous command, which is supported but also has known issues or risks.
Copy file name to clipboardExpand all lines: modules/update-conditional-web-console.adoc
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,12 +22,11 @@ You can view and assess the risks associated with particular updates with condit
22
22
.Procedure
23
23
24
24
. From the web console, click *Administration*->*Cluster settings* page and review the contents of the *Details* tab.
25
-
26
-
. You can enable `Include supported but not recommended versions` in the `Select new version` dropdown of the *Update cluster* modal to populate the dropdown list with conditional updates.
25
+
. You can enable the `Include versions with known issues` feature in the *Select new version* dropdown of the *Update cluster* modal to populate the dropdown list with conditional updates.
27
26
+
28
27
[NOTE]
29
28
====
30
-
If a `Supported but not recommended` version is selected, more information is provided with potential issues with the version.
29
+
If a version with known issues is selected, more information is provided with potential risks that are associated with the version.
31
30
====
32
31
33
32
. Review the notification detailing the potential risks to updating.
Copy file name to clipboardExpand all lines: modules/update-evaluate-availability.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,4 +18,4 @@ The CVO continuously evaluates its cluster characteristics against the condition
18
18
If the CVO finds that the cluster does not match the risks of an update, or that there are no risks associated with the update, it stores the target version in the `availableUpdates` field of its `ClusterVersion` resource.
19
19
20
20
The user interface, either the web console or the OpenShift CLI (`oc`), presents this information in sectioned headings to the administrator.
21
-
Each *supported but not recommended*update recommendation contains a link to further resources about the risk so that the administrator can make an informed decision about the update.
21
+
Each known issue associated with the update path contains a link to further resources about the risk so that the administrator can make an informed decision about the update.
Copy file name to clipboardExpand all lines: modules/update-service-overview.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ To allow the OpenShift Update Service to provide only compatible updates, a rele
19
19
20
20
[IMPORTANT]
21
21
====
22
-
The OpenShift Update Service displays all recommended updates for your current cluster. If an update path is not recommended by the OpenShift Update Service, it might be because of a known issue with the update or the target release.
22
+
The OpenShift Update Service displays all recommended updates for your current cluster. If an update path is not recommended by the OpenShift Update Service, it might be because of a known issue related to the update path, such as incompatibility or availability.
Copy file name to clipboardExpand all lines: modules/update-upgrading-cli.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ endif::openshift-origin[]
66
66
+
67
67
[NOTE]
68
68
====
69
-
* If there are no available updates, updates that are supported but not recommended might still be available.
69
+
* If there are no recommended updates, updates that have known issues might still be available.
70
70
See _Updating along a conditional update path_ for more information.
71
71
ifndef::openshift-origin[]
72
72
* For details and information on how to perform an `EUS-to-EUS` channel update, please refer to the _Preparing to perform an EUS-to-EUS upgrade_ page, listed in the Additional resources section.
0 commit comments