Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8294

[RFE|RHACM] EnhanceMultiClusterHub CR with a Status Message Field for Improved product serviceability

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Enhance MultiClusterHub CR with a Status Message Field for Improved Observability product serviceability.

      2. What is the nature and description of the request?

      This is a feature enhancement request to improve the status reporting of the MultiClusterHub Custom Resource (CR). The proposal is to add a new message field to the .status stanza of the MultiClusterHub Custom Resource Definition (CRD).

      The multiclusterhub-operator would be responsible for populating this new field with a concise, human-readable string that provides context for the CR's current state. This message would describe why the component is Installing, Progressing, Degraded, or Running.

      Furthermore, this new status field should be exposed as a new MESSAGE column in the terminal output of the oc get multiclusterhub command, providing administrators with immediate, at-a-glance insight.

      $ oc get multiclusterhub
      NAME              STATUS     AGE    CURRENTVERSION   DESIREDVERSION   MESSAGE
      multiclusterhub   Degraded   25m    2.13.0           2.13.0           Deployment 'xxxxx' has unavailable replicas 

      3. Why does the customer need this? (List the business requirements here)

      The primary goal is to reduce operational overhead and accelerate troubleshooting.

      • Reduce Mean Time to Resolution (MTTR): Administrators need to diagnose the root cause of an issue faster. A descriptive message provides immediate context, eliminating the initial, time-consuming step of searching through operator logs and events to understand a problem. ⏱️
      • Improve Operational Efficiency: Support engineers and SREs need to quickly and accurately assess the health of an ACM installation. A clear status message makes routine checks more efficient and reduces the cognitive load required to manage the environment.
      • Streamline Support Engagements: When creating a support ticket, customers need to provide accurate and relevant information. A clear error or status message can be easily copied and shared, leading to a more effective and faster support lifecycle.
      • Enable Robust Automation: Automated monitoring and alerting systems require clear, parsable state information. A dedicated message field provides a reliable source for scripts to determine the system's health and trigger appropriate automated actions (e.g., sending a specific alert to PagerDuty).

       
      4. List any affected packages or components.
       
      RHACM{-}observability product serviceability.

              sberens@redhat.com Scott Berens
              rhn-support-dpateriy Divyam Pateriya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None