Epic Goal

As an MCE operator and user, I need comprehensive and accurate status reporting that clearly communicates the current state of my MultiClusterEngine installation, including upgrades, degraded states, and validation failures, so that I can quickly understand system health and take appropriate action....

Why is this important?

• Improved User Experience: Clear status reporting reduces confusion and support tickets
  **
• Better Operational Visibility: SREs can quickly identify and respond to issues
  **
• Reduced MTTR: Faster problem identification through clear status categorization
  **
• Compliance: Aligns with Kubernetes API conventions and operator best practices

Scenarios

• Reduced time-to-resolution for support cases
• Improved user experience during upgrades
• Better operational visibility for cluster administrators
• Clearer indication of when manual intervention is needed

Acceptance Criteria

• [ ] New status phases implemented and documented
• [ ] Phase transitions are logical and well-tested
• [ ] Degraded state is detected and reported
• [ ] Backward compatibility maintained with existing phases
• [ ] Comprehensive test coverage (unit, integration, e2e)
• [ ] Documentation updated (API docs, troubleshooting guide)

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• 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 Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)