Test scenarios

disconnected/using-olm.adoc

@@ -14,8 +14,10 @@ The mirror registry can be located on a bastion host, which requires connectivit
 
 This guide describes the following process that is required to enable OLM in disconnected environments:
 
-* Disable the default remote OperatorHub sources for OLM.
-* Use a workstation with full internet access to create and push local mirrors of the OperatorHub content to a mirror registry.
+* Disable the default remote sources for OLM.
+** For {olmv0}, you must disable the remote OperatorHub catalog sources.
+** For {olmv1}, you must disable the remote cluster catalogs.
+* Use a workstation with full internet access to create and push local mirrors of the content to a mirror registry.
 * Configure OLM to install and manage Operators from local sources on the mirror registry instead of the default remote sources.
 
 After enabling OLM in a disconnected environment, you can continue to use your unrestricted workstation to keep your local OperatorHub sources updated as newer versions of Operators are released.
@@ -63,8 +65,13 @@ The `opm` subcommands, flags, and functionality related to the SQLite database f
 
 Many of the `opm` subcommands and flags for working with the SQLite database format, such as `opm index prune`, do not work with the file-based catalog format. For more information about working with file-based catalogs, see xref:../operators/understanding/olm-packaging-format.adoc#olm-file-based-catalogs_olm-packaging-format[Operator Framework packaging format], xref:../operators/admin/olm-managing-custom-catalogs.adoc#olm-managing-custom-catalogs-fb[Managing custom catalogs], and xref:../disconnected/mirroring/installing-mirroring-disconnected.adoc#installing-mirroring-disconnected[Mirroring images for a disconnected installation using the oc-mirror plugin].
 ====
+[id="olm-mirror-catalog_{context}]
+=== Scenarios for adding catalog contents to a cluster
 
-include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+1]
+The way you mirror your catalog content depends on whether you are using {olmv0} or {olmv1} to manage and lifelcycle Operators and extensions on your cluster. For {olmv0}, you create a catalog source and apply it to a cluster. For {olmv1}, you create a custom resource (CR) for a cluster catalog and apply it to the cluster.
+
+include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+3]
+include::modules/olmv1-adding-a-catalog-to-a-cluster.adoc[leveloffset=+3]
 
 [role="_additional-resources"]
 .Additional resources
@@ -76,4 +83,4 @@ include::modules/olm-creating-catalog-from-index.adoc[leveloffset=+1]
 [id="next-steps_olm-restricted-networks"]
 == Next steps
 
-* xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]
+* xref:../operators/admin/olm-upgrading-operators.adoc#olm-upgrading-operators[Updating installed Operators]