EPIC Goal

The goal is to keep the Operator:

• Multiplatform which mean it has to be generic enough and have enough facilities to be deployed on any K8s cluster with (primary prod option) or without OLM support

• Multiprofile which mean it has to be generic enough and have enough facilities to serve any Backstage application deployment (RHDH is a primary goal). Using default configuration "profile" so it is possible to deploy even empty CR.

Why is this important?

• to cover wider audience and usecases
• as a result better design

User Scenarios

• As an Admin I want to make sure Operator is working on my K8s platform and have full control on deployment configuration
• As a Developer I want to use my favorite local/provided k8s cluster
• As a Platform Engineer I want to configure Backstage with minimal knowledge of K8s resources
• As a User evaluating Backstage I want fast start with predefined settings. 

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>