Updated the catalog resources for oc-mirror v2

Author: subhtk

disconnected/mirroring/about-installing-oc-mirror-v2.adoc

@@ -66,6 +66,8 @@ include::modules/oc-mirror-IDMS-ITMS-about.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
+* xref:../../rest_api/operatorhub_apis/catalogsource-operators-coreos-com-v1alpha1.html[CatalogSource]
+
 * xref:../../rest_api/config_apis/imagedigestmirrorset-config-openshift-io-v1.adoc#imagedigestmirrorset-config-openshift-io-v1[ImageDigestMirrorSet]
 
 * xref:../../rest_api/config_apis/imagetagmirrorset-config-openshift-io-v1.adoc#imagetagmirrorset-config-openshift-io-v1[ImageTagMirrorSet]

modules/oc-mirror-IDMS-ITMS-about.adoc

@@ -18,4 +18,4 @@ The oc-mirror plugin v2 automatically generates the following custom resources:
 
 `ClusterCatalog`:: Retrieves information about the available cluster extensions (which includes Operators) in the mirror registry. Used by {olmv1}.
 
-`UpdateService`:: Provides update graph data to the disconnected environment. Used by the OpenShift Update Service.
+`UpdateService`:: Provides update graph data to the disconnected environment. Used by the OpenShift Update Service.

modules/oc-mirror-updating-cluster-manifests-v2.adoc

@@ -28,6 +28,38 @@ In oc-mirror plugin v2, the IDMS and ITMS files cover the entire image set, unli
 ----
 $ oc apply -f <path_to_oc_mirror_workspace>/working-dir/cluster-resources
 ----
++
+[IMPORTANT]
+====
+When using resources generated by the oc-mirror plugin v2 to configure your cluster, do not change specific fields. Changing them can cause errors and is not supported. 
+
+The following fields must *not* be changed:
+
+[cols="2a,4a", options="header"]
+|===
+|Resource |Fields that must not be changed
+
+|CatalogSource
+|`apiVersion`, `kind`, `spec.image`
+
+|ClusterCatalog
+|`apiVersion`, `kind`, `spec.source.image.ref`
+
+|ImageDigestMirrorSet
+|`apiVersion`, `kind`, `spec.imageDigestMirrors`
+
+|ImageTagMirrorSet
+|`apiVersion`, `kind`, `spec.imageTagMirrors`
+
+|Signature ConfigMap
+|`apiVersion`, `kind`, `metadata.namespace`, `binaryData`
+
+|UpdateService
+|`apiVersion`, `kind`, `spec.graphDataImage`, `spec.releases`
+|===
+
+For more details, refer to the OpenShift API documentation for `CatalogSource`, `ImageDigestMirrorSet`, and `ImageTagMirrorSet`.
+====
 
 . If you mirrored release images, apply the release image signatures to the cluster by running the following command:
 +