Dev process and CI/CD pipeline / build for operator

[planetf1]

Currently the operator is built by running a variety of SDK commands.

We need to identify best practice in terms of the

• developer pipeline for updating the operator
• PR verification when changes are made to the operator
• automated testing framework for the operator
• release of the operator
• publishing to appropriate repositories/marketplaces

Some good starting points may include

• The CI Working group https://github.com/operator-framework/community/blob/master/wg-ci/README.md#meetings
• other operator code examples

• kubernetes-operators on slack

[planetf1]

First attempt to use a github workflow to simply replicate the steps I was undertaking locally, including the setup_go action resulted in '/home/runner/work/egeria-k8s-operator/egeria-k8s-operator/bin/controller-gen: Exec format error' , since the skeleton project setup by the operator includes native code, and the current build environment is macOS.

Soliciting input on best practices at https://groups.google.com/g/operator-framework/c/VDQL4qD-oCY

[planetf1]

A basic approach is in place. The issue above was resolved through questions on the mailing list, and some subsequent improvements to the sdk. Specific issues will be opened for any future improvements once the new operator is established