-
Notifications
You must be signed in to change notification settings - Fork 55
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
operator: stop creating CRD #761
Labels
bug
Something isn't working
Comments
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 9, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) Operator shall not self-register CRDs. So we stop installing/uninstalling the Deployment CRD. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 9, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) Operator shall not self-register CRDs. So we stop installing/uninstalling the Deployment CRD. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 9, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. So we stop doing so. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 9, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. With this change we stop doing so. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 13, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. With this change we stop doing so. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 13, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. With this change we stop doing so. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 13, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. With this change we stop doing so. FIXES: intel#761
avalluri
added a commit
to avalluri/pmem-CSI
that referenced
this issue
Oct 14, 2020
As per operator developer [best-practices](https://github.com/operator-framework/community-operators/blob/master/docs/best-practices.md) the operator shall not self-register CRDs. With this change we stop doing so. FIXES: intel#761
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The approach taken by OLM (= aka installation from Operator Hub) is to create the CRD as part of the installation, i.e. the operator doesn't need to create it and also shouldn't delete it. This is more predictable.
We should do the same when installing the operator via YAML and remove the extra code for managing the CRD.
The text was updated successfully, but these errors were encountered: