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

RHACS: Re-word "Manual Upgrade Required" on clusters page

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      Business Problem:

      _Customers see "Manual Upgrade Required" on their clusters page whenever Central and Secured Clusters versions mismatch. The word "Upgrade" is used, even if the Secured Cluster is on a newer version than Central.
      _

      _With ACS Cloud Service, Central is often on a point release that is behind the current available latest version. Customers using the Operator to auto-upgrade their Secured Clusters see that version advancing while ACS CS waits to adopt the new version.
      _

      Any messaging change should take into account the official "drift" support policy. How far back / ahead can one side be and still function? What can customers do about the mismatch? UI messaging should distinguish between "informational," and "action required"

       

      Use Cases:

      [Describe specific scenarios or situations where the feature would be useful]

       

      Key Functionality:

      [Outline the main functions and capabilities of the feature]

       

      Benefits:

      [Highlight the benefits/advantages of the suggested feature if not addressed above]]

      Acceptance criteria:

      [Describe the key features that need to be covered by the feature to be able to satisfy the customer]

      Implementation Suggestions (optional):

      • Integration: [Specify any existing systems or tools that the new feature should integrate with]

       

      • Dependencies: [Describe any dependencies on other 3rd party integrations or OCP components] 

       

      • User Experience: [Provide suggestions for designing the UI to optimize usability. Highlight other relevant aspects of the user experience ]

       

      Timeline:

      [Specify the preferred implementation date or any specific deadlines for the feature implementation]

       

      Please use the following Jira fields to complete this Feature Request

      1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
      2. [Jira Field] Description:
      3. [Jira Field] Component:
      4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]
      1. [Jira Field] Supporting Documentation:
         
      1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]

       

       

            dcaspin@redhat.com Doron Caspin
            cporter@redhat.com Christopher Porter (Inactive)
            Anjali Telang, Boaz Michaely, Doron Caspin, JP Jung, Maria Simon Marcos, Shubha Badve
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: