Merge pull request #97705 from michaelryanpeter/ocpbugs-60614-restore-olmv1-cli-only-admon

OCPBUGS#60614: OLMv1 Restore OLMv1 CLI only admonition

Author: michaelryanpeter

extensions/catalogs/catalog-content-resolution.adoc

@@ -19,7 +19,11 @@ If you do not specify any catalog selection criteria, {olmv1-first} selects an e
 During resolution, bundles that are not deprecated are preferred over deprecated bundles by default.
 
 include::modules/olmv1-catalog-selection-by-name.adoc[leveloffset=1]
+
 include::modules/olmv1-catalog-selection-by-labels-or-expressions.adoc[leveloffset=1]
+
 include::modules/olmv1-catalog-exclusion-by-labels-or-expressions.adoc[leveloffset=1]
+
 include::modules/olmv1-catalog-selection-by-priority.adoc[leveloffset=1]
+
 include::modules/olmv1-troubleshooting-catalog-selection-errors.adoc[leveloffset=1]

extensions/catalogs/creating-catalogs.adoc

@@ -9,17 +9,20 @@ toc::[]
 Catalog maintainers can create new catalogs in the file-based catalog format for use with {olmv1-first} on {product-title}.
 
 include::modules/olm-creating-fb-catalog-image.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../cli_reference/opm/cli-opm-ref.adoc#cli-opm-ref[`opm` CLI reference]
 
 include::modules/olm-filtering-fbc.adoc[leveloffset=+1]
+
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../operators/understanding/olm-packaging-format.adoc#olm-deprecations-schema_olm-packaging-format[Packaging format -> Schemas -> olm.deprecations schema]
 * xref:../../disconnected/mirroring/installing-mirroring-disconnected.adoc#updating-mirror-registry-content[Mirroring images for a disconnected installation using the oc-mirror plugin -> Keeping your mirror registry content updated]
 * xref:../../disconnected/using-olm.adoc#olm-creating-catalog-from-index_olm-restricted-networks[Adding a catalog source to a cluster]
+
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]

extensions/ce/managing-ce.adoc

@@ -10,31 +10,50 @@ After a catalog has been added to your cluster, you have access to the versions,
 
 You can use custom resources (CRs) to manage extensions declaratively from the CLI.
 
+include::snippets/olmv1-cli-only.adoc[]
+
 include::modules/olmv1-supported-extensions.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
+
 * xref:../../operators/understanding/olm/olm-operatorconditions.adoc#olm-operatorconditions[Operator conditions]
 
 include::modules/olmv1-finding-operators-to-install.adoc[leveloffset=+1]
+
 include::modules/olmv1-catalog-queries.adoc[leveloffset=+2]
+
 include::modules/olmv1-cluster-extension-permissions.adoc[leveloffset=+1]
+
 include::modules/olmv1-creating-a-namespace.adoc[leveloffset=+2]
+
 include::modules/olmv1-creating-a-service-account.adoc[leveloffset=+2]
+
 include::modules/olmv1-downloading-bundle-manifests.adoc[leveloffset=+2]
+
 include::modules/olmv1-required-rbac-to-install-and-manage-extension-resources.adoc[leveloffset=+2]
+
 include::modules/olmv1-creating-a-cluster-role.adoc[leveloffset=+2]
+
 include::modules/olmv1-example-pipelines-operator-cluster-role.adoc[leveloffset=+2]
+
 include::modules/olmv1-creating-a-cluster-role-binding.adoc[leveloffset=+2]
+
 include::modules/olmv1-installing-an-operator.adoc[leveloffset=+1]
+
 include::modules/olmv1-installing-an-operator-in-a-specific-namespace.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
+
 * xref:../../extensions/ce/managing-ce.adoc#olmv1-supported-extensions_managing-ce[Supported extensions]
+
 * xref:../../authentication/using-rbac.adoc#rbac-projects-namespaces_using-rbac[Projects and namespaces]
+
 * xref:../../extensions/ce/managing-ce.adoc#olmv1-creating-a-service-account_managing-ce[Creating a service account]
+
 * xref:../../extensions/ce/update-paths.adoc#olmv1-about-target-versions_update-paths[Example custom resources (CRs) that specify a target version]
+
 * xref:../../extensions/ce/update-paths.adoc#olmv1-version-range-support_update-paths[Support for version ranges]
 
 include::modules/olmv1-troubleshooting-rbac-errors-with-preflight-check.adoc[leveloffset=+1]
@@ -43,6 +62,7 @@ include::modules/olmv1-updating-an-operator.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
+
 * xref:../../extensions/ce/update-paths.adoc#update-paths[Update paths]
 
 include::modules/olmv1-deleting-an-operator.adoc[leveloffset=+1]

extensions/index.adoc

@@ -10,6 +10,8 @@ Extensions enable cluster administrators to extend capabilities for users on the
 
 {olm-first} has been included with {product-title} 4 since its initial release. {product-title} {product-version} includes components for a next-generation iteration of {olm} as a Generally Available (GA) feature, known during this phase as _{olmv1}_. This updated framework evolves many of the concepts that have been part of previous versions of {olm} and adds new capabilities.
 
+include::snippets/olmv1-cli-only.adoc[]
+
 [id="olmv1-highlights_{context}"]
 == Highlights
 

modules/olmv1-installing-an-operator.adoc

@@ -9,6 +9,8 @@
 
 You can install an extension from a catalog by creating a custom resource (CR) and applying it to the cluster. {olmv1-first} supports installing cluster extensions, including {olmv0} Operators in the `registry+v1` bundle format, that are scoped to the cluster. For more information, see _Supported extensions_.
 
+include::snippets/olmv1-cli-only.adoc[]
+
 .Prerequisites
 
 * You have created a service account and assigned enough role-based access controls (RBAC) to install, update, and manage the extension that you want to install. For more information, see "Cluster extension permissions".

snippets/olmv1-cli-only.adoc

@@ -1,7 +1,7 @@
 // Text snippet included in the following modules:
 //
-// * operators/olm_v1/olmv1-installing-an-operator-from-a-catalog.adoc
-
+// * extensions/ce/managing-ce.adoc
+// * extensions/index.adoc
 
 :_mod-docs-content-type: SNIPPET