Skip to content
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

Migrate to from database to declarative index #17

Closed
rtclauss opened this issue Sep 15, 2022 · 1 comment
Closed

Migrate to from database to declarative index #17

rtclauss opened this issue Sep 15, 2022 · 1 comment

Comments

@rtclauss
Copy link
Contributor

rtclauss commented Sep 15, 2022

The existing operator uses a database for the index.

If you attempt to install the StockTrader operator on a cluster that has an OLM version of greater than v0.21.1 you will see failures when deploying the operator and you will see this in the logs somewhere:

Sqlite-based catalogs and their related subcommands are deprecated. Support for
them will be removed in a future release. Please migrate your catalog workflows
to the new file-based catalog format.

A workaround is to install version v0.21.1of OLM in your cluster:

operator-sdk olm install --version=v0.21.1

I believe this means we need to move to the declarative-style of operator index.

https://github.com/operator-framework/enhancements/blob/master/enhancements/declarative-index-config.md#deprecations
operator-framework/olm-docs#177
https://olm.operatorframework.io/docs/reference/file-based-catalogs/

@jwalcorn
Copy link
Member

I made this move several months ago. See the bundle/README.md for details. Let me know if there's still any issue. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants