Cluster ownership transfer for Managed OpenShift clusters

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA)
    • 4.x
  • Red Hat OpenShift Dedicated (OSD)
    • 4.x

Issue

  • The cluster ownership transfer cannot be executed even with Organization Admin permission.
  • As part of an OSD trial, a cluster was provisioned in a personal account and now it needs to be transferred to the corporate account/organization for managing subscriptions.
  • How to transfer the ownership of an OpenShift Dedicated Non-CCS cluster with no cluster-admin privileges.
  • The cluster requires action because it is no longer owned by a user with an enabled Red Hat account.
  • Is it possible to transfer the cluster ownership to a service account instead of a normal user account?

Resolution

  • Within Red Hat Managed Services, cluster ownership transfer via the OCM UI (Access Control / Transfer ownership) is currently only available for ROSA classic architecture clusters. This enables cluster owners to transfer clusters to a new account within the same or a different Organization ID. For more information, please refer to the official ROSA documentation.

  • Red Hat Support must perform the ownership transfer on your behalf in the following scenarios:

    • Where the cluster is OSD (GCP marketplace) and the ownership transfer needs to be done to other users within and across RH organizations;
    • Where the cluster is OSD (other than GCP marketplace) and the ownership transfer needs to be done to other users within the same RH organization;
    • Where the cluster does not have cluster-admin privileges (specifically OSD Non-CCS clusters);
    • Where the cluster is ROSA Hosted Control Plane;
    • Where there is an issue preventing the cluster ownership to be transferred to the new user;
    • Where the new cluster owner is a service account;
    • Where the owner is banned.

    When raising the support case with Red Hat, please provide the following information:

    clusterID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Current Owner:
Username: [user_name]
Email: [email]
Account ID: [account_id]

New Owner:
Username: [user_name]
Email: [email]
Account ID: [account_id]

    The information about the User, Email and Account ID can be seen in the Red Hat Customer Portal, by clicking on the "avatar" in the top right of the page. For a Service Account, please refer to the Service Accounts tab in Identity & Access Management.

    If the transferring needs to be done to a service account, the username comes with this format service-account-<Client ID> (e.g.,service-account-edcf4859-37d1-42e2-8b11-8e3927a6a788). So, it is required that the Client ID is also provided.

    Use the following command to get the clusterID if required:

    $ oc get clusterversion -o yaml | grep clusterID

Important: The cluster ownership transfer triggers the nodes replacement due to the new machineconfig rendering. So, this process will first deploy new nodes and then the old ones drained and deleted.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments