Github Issues for Component RHODS Operator for release rhods-2.4

1.  [Luca - Verified]Verify cleanup of KfDef instances.
2. [Luca - Verified] Update V2 Operator to account for Distributed Workloads deployment update
3. [N/A - Not in 2.4] Updating the monitoring namespace in the DSCI CR leaves resources running
4. [N/A] [tracker]: transition for manifests for downstream components
5. [N/A] Update Dockerfile to include component manifests
6. [Luca - Failed QA] Verify cleanup of odh-deployer resources.
7.  [N/A?]Track Efforts to add support for managed platform
8. [Luca - Verified] Codeflare - RHODS Reconciliation error after roles update
9.  [Luca - partially verified] Model Mesh cannot work together in the cluster where Kserve was first enabled
10.  [Luca - Verified] Add Trusty AI component
11. [Jorge - FAILED QA, see RHODS-12867] Monitoring and Alerting requirements for existing managed stack
12.  [Luca - N/A]Track Efforts to move from odh-deployer to operator
13. [N/A- Moved to 2.5] Add missing resources to manage in DSC controller   
14. [Luca - Failed QA due to point 6] Track changes for automatic upgrade path

Issues found after RC1

1. [Adrian - Verified] Turn off Tech Preview Components
2. [Adrian - Failed] Fix Dashboard 500: Internal Error
3. [Adrian - Failed] https://issues.redhat.com/browse/RHODS-12812  codeflare alerts firing
4. [Does not need QE Verification] https://issues.redhat.com/browse/RHODS-12860 for sync findings
5. [Jorge - Verified] RHODS-12867-Metrics rhods_aggregate_availability, rhods_total_users and ALERTS not federated to OpenShift Monitoring
6. [Not fixed on 2.4 RC2] https://github.com/opendatahub-io/opendatahub-operator/issues/587 - duplicate configmaps for DSPO after upgrade