diff --git a/docs/concepts/controlling-catalog-selection.md b/docs/concepts/controlling-catalog-selection.md index 68d19c2b3..13b782d0f 100644 --- a/docs/concepts/controlling-catalog-selection.md +++ b/docs/concepts/controlling-catalog-selection.md @@ -125,7 +125,7 @@ When multiple catalogs provide the same package, you can set priorities to resol In your `ClusterCatalog` resource, set the `priority` field: ```yaml -apiVersion: catalogd.operatorframework.io/v1alpha1 +apiVersion: olm.operatorframework.io/v1alpha1 kind: ClusterCatalog metadata: name: high-priority-catalog @@ -160,7 +160,7 @@ If the system cannot resolve to a single bundle due to ambiguity, it will genera 1. **Create or Update `ClusterCatalogs` with Appropriate Labels and Priority** ```yaml - apiVersion: catalogd.operatorframework.io/v1alpha1 + apiVersion: olm.operatorframework.io/v1alpha1 kind: ClusterCatalog metadata: name: catalog-a @@ -175,7 +175,7 @@ If the system cannot resolve to a single bundle due to ambiguity, it will genera ``` ```yaml - apiVersion: catalogd.operatorframework.io/v1alpha1 + apiVersion: olm.operatorframework.io/v1alpha1 kind: ClusterCatalog metadata: name: catalog-b diff --git a/docs/getting-started/olmv1_getting_started.md b/docs/getting-started/olmv1_getting_started.md index 1156bc968..efffddde8 100644 --- a/docs/getting-started/olmv1_getting_started.md +++ b/docs/getting-started/olmv1_getting_started.md @@ -35,7 +35,7 @@ To create the catalog, run the following command: ```bash # Create ClusterCatalog kubectl apply -f - <