openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS#12905: Resolving content from multiple catalogs

Browse Source
This commit is contained in:
Michael Ryan Peter
2025-02-10 10:35:06 -05:00
committed by openshift-cherrypick-robot
parent 4f4b88c76d
commit 7ba2c6569f
8 changed files with 339 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
extensions/catalogs/catalog-content-resolution.adoc Normal file
View File

@@ -0,0 +1,25 @@
:_mod-docs-content-type: ASSEMBLY
[id="catalog-content-resolution"]
= Catalog content resolution
include::_attributes/common-attributes.adoc[]
:context: catalog-content-resolution
toc::[]
When you specify the cluster extension you want to install in a custom resource (CR), {olmv1-first} uses catalog selection to resolve what content is installed.
You can perform the following actions to control the selection of catalog content:
* Specify labels to select the catalog.
* Use match expressions to perform complex filtering across catalogs.
* Set catalog priority.
If you do not specify any catalog selection criteria, {olmv1-first} selects an extension from any available catalog on the cluster that provides the requested package.
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]