@@ -18,7 +18,7 @@ To select a specific catalog by name, you can use the `matchLabels` field in you
1818#### Example
1919
2020``` yaml
21- apiVersion : olm.operatorframework.io/v1alpha1
21+ apiVersion : olm.operatorframework.io/v1
2222kind : ClusterExtension
2323metadata :
2424 name : my-extension
@@ -39,7 +39,7 @@ If you have catalogs labeled with specific metadata, you can select them using `
3939# ### Using `matchLabels`
4040
4141` ` ` yaml
42- apiVersion: olm.operatorframework.io/v1alpha1
42+ apiVersion: olm.operatorframework.io/v1
4343kind: ClusterExtension
4444metadata:
4545 name: my-extension
@@ -125,7 +125,7 @@ When multiple catalogs provide the same package, you can set priorities to resol
125125In your `ClusterCatalog` resource, set the `priority` field :
126126
127127` ` ` yaml
128- apiVersion: olm.operatorframework.io/v1alpha1
128+ apiVersion: olm.operatorframework.io/v1
129129kind: ClusterCatalog
130130metadata:
131131 name: high-priority-catalog
@@ -160,7 +160,7 @@ If the system cannot resolve to a single bundle due to ambiguity, it will genera
1601601. **Create or Update `ClusterCatalogs` with Appropriate Labels and Priority**
161161
162162 ` ` ` yaml
163- apiVersion: olm.operatorframework.io/v1alpha1
163+ apiVersion: olm.operatorframework.io/v1
164164 kind: ClusterCatalog
165165 metadata:
166166 name: catalog-a
@@ -175,7 +175,7 @@ If the system cannot resolve to a single bundle due to ambiguity, it will genera
175175 ` ` `
176176
177177 ` ` ` yaml
178- apiVersion: olm.operatorframework.io/v1alpha1
178+ apiVersion: olm.operatorframework.io/v1
179179 kind: ClusterCatalog
180180 metadata:
181181 name: catalog-b
0 commit comments