-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 fix(docs): fix apiVersion for clustercatalogs. Replace 'catalogd.operatorframework.io/v1alpha1' with 'olm.operatorframework.io/v1alpha1' #1433
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1433 +/- ##
==========================================
- Coverage 73.45% 73.26% -0.20%
==========================================
Files 42 42
Lines 3063 3063
==========================================
- Hits 2250 2244 -6
- Misses 640 644 +4
- Partials 173 175 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Thanks for reviewing with fresh eyes!
@@ -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: clustercatalogs.olm.operatorframework.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drop the clustercatalogs.
prefix. That's the plural resource name, not part of the apiGroup.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh boy, you have a good catcher too :
I did the test, create the title with the right apiVersion but I did the replace wrong :-P
) $ kubectl get crds | grep clustercatalog
clustercatalogs.olm.operatorframework.io 2024-11-06T21:34:38Z
camiladeomacedo@camilas-MacBook-Air ~/go/src/github.com/operator-framework/operator-controller (fix-install-script) $ kubectl apply -f - <<EOF
> apiVersion: olm.operatorframework.io/v1alpha1
> kind: ClusterCatalog
> metadata:
> name: operatorhubio
> spec:
> source:
> type: Image
> image:
> ref: quay.io/operatorhubio/catalog:latest
> pollInterval: 10m
> EOF
clustercatalog.olm.operatorframework.io/operatorhubio configured
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done! Thanks.
Stopping for today to avoid missing any boats—at least for today. :-)
565b9d4
to
d2c9f5c
Compare
Replace `apiVersion: catalogd.operatorframework.io/v1alpha1` with `apiVersion: olm.operatorframework.io/v1alpha1` for `clustercatalogs.olm.operatorframework.io`. Reason: The API version referenced in the docs appears incorrect. After installing, the correct API name is confirmed with: ``` $ kubectl get crds | grep clustercatalog clustercatalogs.olm.operatorframework.io 2024-11-06T21:34:38Z ``` The API is listed under `clustercatalogs.olm.operatorframework.io`, not `catalogd`. Example error faced when trying to apply with the incorrect API name: ``` $ kubectl apply -f - <<EOF > apiVersion: catalogd.operatorframework.io/v1alpha1 > kind: ClusterCatalog > metadata: > name: operatorhubio > spec: > source: > type: Image > image: > ref: quay.io/operatorhubio/catalog:latest > pollInterval: 10m > EOF error: resource mapping not found for name: "operatorhubio" namespace: "" from "STDIN": no matches for kind "ClusterCatalog" in version "catalogd.operatorframework.io/v1alpha1" ensure CRDs are installed first ``` For reference, see the correct API name here: [olm.operatorframework.io_clustercatalogs.yaml](https://github.com/operator-framework/catalogd/blob/main/config/base/crd/bases/olm.operatorframework.io_clustercatalogs.yaml).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Thanks for fixing it.
d2c9f5c
to
ec47a13
Compare
481bd5d
Replace
apiVersion: catalogd.operatorframework.io/v1alpha1
withapiVersion: olm.operatorframework.io/v1alpha1
forclustercatalogs.olm.operatorframework.io
.Reason:
The API version referenced in the docs appears incorrect. After installing, the correct API name is confirmed with:
The API is listed under
clustercatalogs.olm.operatorframework.io
, notcatalogd
.Example error faced when trying to apply with the incorrect API name:
For reference, see the correct API name here:
olm.operatorframework.io_clustercatalogs.yaml.