Merge pull request #43897 from sagidlow/ISSUE-43384

ISSUE-43384: Removing ConfigMap handling from restricted network cluster doc

Author: sagidlow

updating/updating-restricted-network-cluster.adoc

@@ -46,17 +46,6 @@ include::modules/installation-adding-registry-pull-secret.adoc[leveloffset=+2]
 
 include::modules/update-mirror-repository.adoc[leveloffset=+2]
 
-[id="updating-restricted-network-image-signature-configmap"]
-=== Creating the image signature config map
-
-Before you update your cluster, you must manually create a config map that contains the signatures of the release images that you use. This signature allows the Cluster Version Operator (CVO) to verify that the release images have not been modified by comparing the expected and actual image signatures.
-
-If you are upgrading from version 4.4.8 or later, you can use the `oc` CLI to create the config map. If you are upgrading from an earlier version, you must use the manual method.
-
-//include::modules/update-oc-configmap-signature-verification.adoc[leveloffset=+2]
-
-include::modules/update-configuring-image-signature.adoc[leveloffset=+2]
-
 include::modules/machine-health-checks-pausing.adoc[leveloffset=+3]
 
 include::modules/update-restricted.adoc[leveloffset=+2]