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

Multiple hub architecture for a managed cluster (Klusterlet)

XMLWordPrintable

      Epic Goal

      • Allow a cluster to be registered to multiple hubs

      Note: This Epic does not Have a Dev Preview, Tech Preview, or GA attached because it will not be an officially supported ACM feature

      Why is this important?

      Service Delivery plans to adopt ACM to help with managing their fleet of OCP-as-a-Service clusters.  This creates a scenario where a managed OCP cluster would need to be managed by the SD ACM Hub, but also needs to be able to be registered into a customer's own ACM hub.

      Scenarios

      • OpenShift Cluster Manager (Service Delivery) deploys and manages a customer's ROSA/OSD/ARO/ROKS cluster with a Service Delivery-owned RHACM hub cluster.
      • A user can import the cluster (from first bullet) into their own RHACM hub.

      Acceptance Criteria

      • Standard OCP deployments (Hive-based) must be supported
      • Hosted OCP deployments (HyperShift-based) must be supported
      • The RHACM user's product experience is not degraded, reduced, limited, or changed from existing implementation.
      • Support two hub connections to a ManagedCluster, each defined scope of access. (ie. Admin for 1x and limited resources for the second)
      • This feature should NOT be added to official RHACM product documentation or product blogs
      • This feature should NOT be marketed or advertised as a supported feature of RHACM
      • Internal documentation will be created for Service Delivery to implement this pattern

      Dependencies (internal and external)

      1. None

      Previous Work (Optional):

      1. Work on hosted mode Klusterlet

      Open questions::

           1. Review with security

                 * Initial approach

                 * Final implementation

      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 - Downstream documentation merged: <link to meaningful PR>

              showeimer Sho Weimer
              showeimer Sho Weimer
              Yuanyuan He Yuanyuan He
              Qiu Jian Qiu Jian (Inactive)
              Qiu Jian Qiu Jian (Inactive)
              Sho Weimer Sho Weimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: