1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Files
openshift-docs/modules/update-restricted.adoc
2023-07-21 17:13:54 +00:00

47 lines
1.7 KiB
Plaintext

// Module included in the following assemblies:
//
// * updating/updating_a_cluster/updating_disconnected_cluster/disconnected-update.adoc
:_content-type: PROCEDURE
[id="update-restricted_{context}"]
= Updating the disconnected cluster
Update the disconnected cluster to the {product-title} version that you downloaded the release images for.
//TODO: Add xrefs in the following note when functionality is enabled.
[NOTE]
====
If you have a local OpenShift Update Service, you can update by using the connected web console or CLI instructions instead of this procedure.
====
.Prerequisites
* You mirrored the images for the new release to your registry.
* You applied the release image signature ConfigMap for the new release to your cluster.
+
[NOTE]
====
The release image signature config map allows the Cluster Version Operator (CVO) to ensure the integrity of release images by verifying that the actual image signatures match the expected signatures.
====
* You obtained the sha256 digest for your targeted release image.
* You installed the OpenShift CLI (`oc`).
* You paused all `MachineHealthCheck` resources.
.Procedure
* Update the cluster:
+
[source,terminal]
----
$ oc adm upgrade --allow-explicit-upgrade --to-image ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}@<digest> <1>
----
<1> The `<digest>` value is the sha256 digest for the targeted release image, for example, `sha256:81154f5c03294534e1eaf0319bef7a601134f891689ccede5d705ef659aa8c92`
+
If you use an `ImageContentSourcePolicy` for the mirror registry, you can use the canonical registry name instead of `LOCAL_REGISTRY`.
+
[NOTE]
====
You can only configure global pull secrets for clusters that have an `ImageContentSourcePolicy` object. You cannot add a pull secret to a project.
====