Added a note to skip the deletion of operator catalog.

Author: subhtk

modules/oc-mirror-workflows-delete-v2.adoc

@@ -48,3 +48,10 @@ Consider using the mirror-to-disk and disk-to-mirror workflows to reduce mirrori
 In the image delete workflow, oc-mirror plugin v2 deletes only the manifests of the images, which does not reduce the storage occupied in the registry.
 
 To free up storage space from unnecessary images, such as those with deleted manifests, you must enable the garbage collector on your container registry. With the garbage collector enabled, the registry will delete the image blobs that no longer have references to any manifests, thereby reducing the storage previously occupied by the deleted blobs. Enabling the garbage collector differs depending on your container registry. 
+
+[IMPORTANT]
+====
+To skip deleting the Operator catalog image when deleting images, you must list the specific Operators under the Operator catalog image in the `DeleteImageSetConfiguration` file. This ensures that only the specified Operators are deleted, not the catalog image.
+
+If only the Operator catalog image is specified, all Operators within that catalog, as well as the catalog image itself, will be deleted.
+====