WHAT

Observability ConfigMap acceptance status should be used for MKA Status

WHY

When Observability secret is expired, MKA's status typically shows as progressing but does not explain why it is failed. This has been observed many times in kas-installer like environments.

HOW

Observability Operator adds an annotation to the ConfigMap: "observability-operator/status" it's value will be "accepted" when the configuration, including Observatorium configuration is valid. If this annotation is missing, then the config is either invalid or has not been processed a more detailed error message is available in the Observability CR status block

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