WHAT

Multi-Tenancy scenarios need to be tested to accommodate RHOC Observability needs

WHY

RHOSAK and RHOC need to be using a single instance of Observability stack. (Prometheus, Grafana, Alert Manager)

HOW

Per pbraun@redhat.com the feature is developed but not fully tested. If this solution is not verified then we might forced to use OBO operator for the RHOC MVP integration.

DONE

Include the following where applicable:

• <bulleted list of functional acceptance criteria that need to be completed>
• <call out anything on the documentation side that's needed as a result of this task being completed>
• <any metrics, monitoring dashboards and alerts that need to be created or be updated>
• <SOP creation or updates>

Guidelines

The following steps should be adhered to:

• Required tests should be put in place - unit, integration, manual test cases (if necessary)
• CI and all relevant tests passing
• Changes have been verified by one additional reviewer against:
• each required environment
• each supported upgrade path
• If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged