Feature Overview (aka. Goal Summary)  

There are many cases where a customer needs to transfer ownership of their clusters from one user to another user. The current process for transferring ownership of OpenShift clusters requires customers to update the pull secrets on the cluster. This is inconvenient for OCP clusters and blocked on OSD/ROSA clusters as it requires cluster-admin access.

We have already implemented the changes to automate the process of updating the pull secrets on the OpenShift cluster. We now need to make this functionality available to customer via console and CLI so that they can initiate the cluster ownership transfer via self-service.

We should send cluster notifications when we identify clusters where the Red Hat account of the cluster owner is not active.

There are additional areas of impact when the cluster owner RH account becomes inactive:

• we no longer receive/accept telemetry metrics for the clusters as the validation on OCM fails
• the customer is unable to scale up their clusters since the pull secrets associated with the cluster are blocked and cannot be used to pull registry content

Goals (aka. expected user outcomes)

The goal is to simplify the process of transferring cluster ownership, making it available to customers via self-service, and notifying customers when clusters within their their organization are owned by team members that no longer have active Red Hat accounts.

Requirements (aka. Acceptance Criteria):

• Allow customers to initiate cluster ownership transfer requests for OCP clusters to other users within the same or different organization via self-service through OCM without the need to modify the pull secrets on the OpenShift cluster
• Allow customers to initiate cluster ownership transfer requests for OSD / ROSA clusters to other users within the same organization via self-service through OCM without the need to modify the pull secrets on the OpenShift cluster 
• Send a service log notification for the cluster when the Red Hat account of the cluster owner is no longer active
• A proactive support case should be opened for SRE/CEE to engage with the customer to get the cluster ownership transferred to another member of the team
• Continue to accept telemetry metrics for clusters with inactive/banned cluster owners. This is especially important for our ability to bill the customer for cluster or addon usage if the billing is based on consumption where RH does the metering.
• Cluster ownership transfer to a new user in the same org when an owner is banned

Out of Scope

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.