Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-136

Provide a path to transfer ownership for unsupported clusters

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • A-Team
    • Provide a path to transfer ownership for unsupported clusters
    • False
    • False
    • To Do
    • XCMSTRAT-293 - Cluster ownership transfer process improvements
    • XCMSTRAT-293Cluster ownership transfer process improvements
    • 69% To Do, 13% In Progress, 19% Done

      User Story

      As a customer, I want to see options to upgrade or take action on my unsupported cluster or trial. If I signed up through a personal account instead of my organization, I should be prompted to transfer cluster ownership to my org admin or take action around my subscription. 

      Acceptance Criteria

      • When users are notified about upcoming trial expirations, they should be incentivized and prompted to take an appropriate action in the:
        • OCM cluster list
        • OCM cluster details
        • OCP cluster settings (already done as part of CONSOLE-2280) 
      • If no subscriptions exist, we should make it easy to transfer cluster ownership through the UI without necessarily retrieving the pull secret. Offer Account ID or Email as alternative option and provide a way for users to view, edit, cancel throughout the transfer process. 
      • For OSD, this flow should be available as well, however we should block transfers when no support is available at the destination account (instead of warning in the case of OCP) 

      Background

      Currently are ~2000 unclassified clusters. Having clusters in an unclassified state means that Red Hat does not understand what Custom Global Customer Name (GCN) the cluster is associated with. This limits Red Hat’s ability to engage with the owner of the cluster in a meaningful way which decreases chances of revenue generation, retention, and customer success. There are several scenarios by which these unclassified clusters can occur. One key scenario is the group that is creating a cluster outside of their existing org and never taking action to transfer to the right place where RH would have visibility to engage. See slides for details: Unclassified Clusters Overview 

      Design

      Transfer cluster ownership - Auth token (outdated)

      ^If needed. Pull secret could also work for this option but sharing your pull secret (current implementation) has security concerns

      Transfer cluster ownership - Approval flow (outdated)

      Latest designs:
      Mocks

       

      cc crobson@redhat.comkhatchousmordech@redhat.com, dramakri@redhat.com, kdoberstrhn-engineering-gsheremedayle.parker, rhn-engineering-abhgupta 

            rh-ee-kcormier Kevin Cormier
            chart@redhat.com Colleen Hart
            HAC
            Votes:
            0 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: