Spike Investigation

Research how the Shipwright operator upstream should be structured so that we have a sustainable development model upstream and adequately support OLM v1, which is expected to be released GA with OpenShift 4.18.

See also OCPSTRAT-1347

Objectives

Answer the following:

• Should we continue to use `operator-sdk` as the tool for organizing the operator codebase upstream?
• If yes, what changes are needed to the operator to make it be supported by the latest operator-sdk version?
• If no, what should replace it? Ex: can we use Helm to deploy the operator.
• Should we continue to use manifestival to deploy operands?
• What changes would make it easier to consume shipwright-io/operator downstream in the builds operator?

Ref: https://docs.google.com/document/d/1UpBLZFGONj-e9aDTvWFdlGKLnaIhTZQr-wOWcs6lGCI/edit?tab=t.0#heading=h.y02czw19ankp

Additional Info

• Upstream tech debt feature: https://github.com/shipwright-io/operator/issues/139
• Upstream bug related to obsolete version of operator-sdk: https://github.com/shipwright-io/operator/issues/212