Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-4875

RFE: Enhance the ManagedCluster CR to include Node status and addon operator versions

XMLWordPrintable

    • False
    • None
    • False
    • Green
    • 0% To Do, 0% In Progress, 100% Done

      The ManagedCluster CR provides very useful data back on the hub/management cluster that would allow automation tools and dashboards built by the customer from a central location determine:

      1. Current OCP Version of managed clusters
      2. Node level allocatable resources

      The request is to enhance this CR to include:

      1. Current node status (Ready, Ready/Unscheduable, NotReady etc) - TENTATIVELY APPROVED
        • Server Foundation:
          • Include a new status in ManagedCluster when the cluster is a single node, and return and synchronize the status of the node.
      2. Addon Operators and their version (SRIOV, PTP, FEC, etc) - TENTATIVELY DENIED
        • Server Foundation:
          • As discussed in other threads, it is not feasible or scalable to watch and synchronize all or even a specific set of OLM operators to the ManagedCluster resource, and especially for a specific customer's use case.  The OLM operators listed can use other mechanisms such as the ClusterClaims API to provide the information themselves to synchronize back to the ManagedCluster resource, which will automatically be able to be leveraged in Placement.

      The enhancement provides the automation team to then:

      1. Dynamically update a ClusterGroupUpgrade CRD to exclude clusters with a node status of anything other then Ready
      2. Dynamically update the ClusterGroupUpgrade CRD to include or exclude clusters based on OCP Version, Operator Versions etc

      The main goal would be to have a central database to query for data that is pertinent to making the entire solution more flexible.

      Market Problem

      ...

      Why it Matters

      ...

      Illustrative User Stories or Scenarios

      ...

      Expected Outcomes

      This Section: Articulates and defines the value proposition from a users
      point of view

      ...

      Effect

      ...

      Challenges and Open Questions:

      ...

      Partner

      This Section: Partner is any specific delivery vehicle requirement.
      These are feature components that MUST be delivered in concert with or
      through a particular BU external product.

      This represents part of the “how” statement for a feature. This would be
      the optional only category.

      • ...

      Additional/tangential areas for future development (TBK)

              zxue@redhat.com ZHAO XUE
              rhn-gps-ncocker Nabeel Cocker
              Hui Chen Hui Chen
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: