Tips on updating OperatorHub

Updating Community OperatorHub

After making changes to the SusQL Operator, we will want to then update the images available from the Community OperatorHub. (Tip: if you have been testing with images and files pushed to your personal repository, be sure that the bundle yaml files you will push to OperatorHub no longer container references to your personal repository.)

Operations in the sustainable-computing-io/susql-operator repository

• Bump up the version in susql-operator/VERSION
• make bundle
• Push updated files to the main branch of the sustainable-computing-io/susql-operator repository.

Operations in your community OperatorHub fork

• Fork and clone https://github.com/k8s-operatorhub/community-operators
• Create a directory in operators/susql-operator in your community-operators fork that matches the susql-operator/VERSION file. e.g., if you are creating version 0.0.42 then mkdir operators/susql-operator/0.0.42
• Copy directory structure under the SusQL Operator Repo susql-operator/bundle to the community operator Repo operators/susql-operator/<yourversion> e.g., cd ~git/<YOUROPERATORHUBFORK>/operators/susql-operator/0.0.42 && cp -r ~/git/susql-operator/bundle/* .
• Do the usual git add, git commit -sm, git push in your community-operators fork.
• Click on the contribute button in your github community-operator fork, and follow the process to submit a pull request.