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: updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update-osus.adoc
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,13 @@ The release image signature config map allows the Cluster Version Operator (CVO)
135
135
====
136
136
* The current release and update target release images are mirrored to a locally accessible registry.
137
137
* A recent graph data container image has been mirrored to your local registry.
138
+
* A recent version of the OpenShift Update Service Operator is installed.
139
+
+
140
+
[NOTE]
141
+
====
142
+
If you have not recently installed or updated the OpenShift Update Service Operator, there might be a more recent version available.
143
+
See xref:../../../operators/admin/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks] for more information about how to update your OLM catalog in a disconnected environment.
144
+
====
138
145
139
146
After you configure your cluster to use the locally-installed OpenShift Update Service and local mirror registry, you can use any of the following update methods:
0 commit comments