Epic Goal

Improve the user experience of Builds for OpenShift operator installation

Acceptance Criteria (Mandatory)

• Name of the operator is displayed as "Builds for OpenShift" in the operatorhub
• The operator description links go to official docs (instead of GitHub)
• The operator gets installed in the "openshift-builds" namespace (currently it is installed in "openshift-operator" namespace) (see KCS article).
• When Builds for OpenShift operator gets installed, the operator automatically deploys the Shipwright control plane (currently user should create an additional CR after installing the operator). Namespace creations should get delegated to OLM instead of the operator

Dependencies (internal and external)

TBD

Open questions::

TBD

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment