OSDOCS#8882 OLM 1.0 admonition for multicatalog conflicts

michaelryanpeter · michaelryanpeter · commit 428eef25683e · 2024-02-02T11:00:42.000-05:00
diff --git a/modules/olmv1-about-catalogs.adoc b/modules/olmv1-about-catalogs.adoc
@@ -9,3 +9,5 @@
 = About catalogs in {olmv1}
 
 You can discover installable content by querying a catalog for Kubernetes extensions, such as Operators and controllers, by using the catalogd component. Catalogd is a Kubernetes extension that unpacks catalog content for on-cluster clients and is part of the {olmv1-first} suite of microservices. Currently, catalogd unpacks catalog content that is packaged and distributed as container images.
+
+include::snippets/olmv1-multi-catalog-admon.adoc[]
diff --git a/snippets/olmv1-multi-catalog-admon.adoc b/snippets/olmv1-multi-catalog-admon.adoc
@@ -0,0 +1,13 @@
+// Text snippet included in the following modules:
+//
+// * modules/olmv1-about-catalogs.adoc
+
+:_mod-docs-content-type: SNIPPET
+
+[IMPORTANT]
+====
+If you try to install an Operator or extension that does not have unique name, the installation might fail or lead to an unpredictable result. This occurs for the following reasons:
+
+* If mulitple catalogs are installed on a cluster, {olmv1} does not include a mechanism to specify a catalog when you install an Operator or extension.
+* Dependency resolution in {olmv1-first} requires that all of the Operators and extensions that are available to install on a cluster use a unique name for their bundles and packages.
+====
