Remove Grafana Operator as it is only community managed which will make us vunerable to CVEs, bug and product updates. 

High Level steps: 

Remove the use of the Grafana Operator from Integr8tly and replace it with a productized Grafana image.  This will require a new Deployment. Copy the deployment that is created by the Operator - removing the init container.

Instead of creating Grafana CRs, we can use the Grafana API to create the rate limiting dashboard and the Grafana data source. 

Use the Package Operator

Considerations: 

Upgrades - any concerns here? 

Reconcile - Reconcile on every Integ8tly reconcile, ensure Deployment exists, call the api, if dashboard and / or datasource don't exist then create.

Which Images to use, proxy and grafana

Jiras

1. POC - Create a new Deployment based on the Operator deployment and strip out the init container - strip down the Deployment as much as possible.

2. Create a single configmap for all dashboards. 1 For RHOAM and later Jira several for 3scale, see here

3. Package Operator Work - Use [fleetshard|https://gitlab.cee.redhat.com/service/managed-tenants-bundles/-/tree/main/addons/acs-fleetshard/package] 

as the example (maybe multiple JIRAs here)

4. Refactor RHOAM code, to remove operator and use Package Operator + test updates 

5. Add the 3scale Dashboards, see here - dependant on MGDAPI-5962

6. Workloads Web Apps - using CRs to create dashboards - use a configmap instead.