Uploaded image for project: 'Red Hat Cluster Management Cloud Services'
  1. Red Hat Cluster Management Cloud Services
  2. CMCS-13

Cluster Registration Cloud Service - Beta

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • Milestone 5
    • None
    • Compute
    • None
    • Cluster Registration Cloud Service - Beta
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Moved to:  https://issues.redhat.com/browse/CMCS-40 


      For AppStudio Beta

      Also known as "Singapore Gateway Service"

      Slack:  #forum-acm-singapore-gateway-service

      Problem statement: 

      Bringing a cluster into the AppStudio experience today that is not part of the DevSandbox.  AppStudio could build a registration flow, but they would rather consume one. This means providing cluster details to AppStudio, either from BYO self-managed or from Service Delivery.

      Timelines:

      • Internal Preview with AppStudio Dev Team - Mid-April (TBD)
      • External closed Beta alongside AppStudio - June (TBD) (40-50 users)

      Beta Requirements:

      • AppStudio users are provisioned a single workspace and are the single user in that workspace. Clusters are scoped to the workspace. Post beta, with KCP, there will be a hierarchy of workspaces where you have an organization-level workspace containing many team workspaces. At that point, the cluster may be scoped to the organization so you only have to import it once and can use across workspaces. TBD later (post-beta).
      • Per discussion March 18 with Jessica Forrester we can assume all clusters in the beta will be OCM clusters available on public Internet. We do NOT need to support private network/reverse proxy in this timeframe.
      • The list of clusters the user can select from for their Environments will be populated from our registration service. There is no concept of trying to use an OCM cluster that has NOT been registered with our service in an environment.

      Architecture

      Architecture Diagram (Miro) 

      Singapore Gateway Service

      The Singapore Gateway Service will initially be built as an integrated component of AppStudio (operator running on AppStudio member clusters) backed by one (or many) large MCE(s) provided via OCM. 

      ManagedClusters reside on a single large MCE, or one MCE per AppStudio member cluster, or potentially (but unlikely we’ll grow this big before KCP) multiple MCE clusters (could be per AppStudio member cluster or shared across the member clusters).

      Note: This may not be the same architecture used in the KCP-based AppCloud implementation

      Resources:

      Singapore Gateway Service

      Registration Service for AppStudio

      Cluster Registration - API Contract

      Architecture Diagram (Miro) 

      SGS Useful Links

      Google Drive

              showeimer Sho Weimer
              sberens@redhat.com Scott Berens
              Brian King Brian King
              Timothy Pouyer Timothy Pouyer
              Joshua Packer Joshua Packer
              Sho Weimer Sho Weimer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: