Chapter 4. Managing your clusters

Every OpenShift cluster is assigned an ID (in the form of a UUID) when created, but each cluster also has an internal cluster identifier used by OpenShift Cluster Manager. The internal cluster identifier can be changed to a human-readable name displayed in OpenShift Cluster Manager if desired.

You can find this information in OpenShift Cluster Manager, using the command line, or in the OpenShift web console.

Additionally, when OpenShift Container Platform clusters register to OpenShift Cluster Manager, the only identifying information may be the cluster UUID. If multiple OpenShift Container Platform clusters have been registered at the same time, it might be necessary to use the cluster UUID to tell them apart.

$ oc get clusterversion <version> -o jsonpath='{.spec.clusterID}{"\n"}'

An image pull secret provides authentication for the cluster to access services and registries which serve the container images for OpenShift components. Every individual user gets a single pull secret generated.

The pull secret is used when installing an OpenShift Container Platform cluster. It is also used by OpenShift Cluster Manager to identify a specific Red Hat user when transferring cluster ownership. To transfer a cluster to another owner, you need to download the pull secret for the user that will take ownership of the cluster.

You can now use this pull secret to create an OpenShift Container Platform cluster or for transferring cluster ownership.

An image pull secret provides authentication for the cluster to access services and registries which serve the container images for OpenShift components. Every individual user gets a single pull secret generated.

The pull secret is used when installing an OpenShift Container Platform cluster and when transferring cluster ownership.

To transfer a connected cluster to a new owner, you must update the pull secret on a cluster to the new owner’s pull secret after initiating a cluster transfer in OpenShift Cluster Manager. The pull secret must be updated within five days of initiating the transfer process, or the process will need to be initiated again from OpenShift Cluster Manager. See Section 4.5, “Transferring cluster ownership”.

This begins updates to all nodes in the cluster, which can take some time depending on the size of your cluster.

You can create a new pull secret in certain cases. For example, if your current pull secret is not working, or if you need a new pull secret for security reasons.

To create a new pull secret, follow the instructions in the KCS article How to request pull-secret rotation.

You can transfer ownership of a connected OpenShift Container Platform cluster to another user in your organization or a different organization using OpenShift Cluster Manager.

To transfer a connected cluster to another owner, you must:

You have now initiated the ownership transfer. The next step is to change the cluster’s pull secret to the pull secret of the new cluster owner.

You can transfer ownership of a disconnected OpenShift Container Platform cluster to another user in your organization or a different organization using OpenShift Cluster Manager.

To transfer ownership of a disconnected cluster, you only need to initiate the transfer in OpenShift Cluster Manager.

When the cluster registers to OpenShift Cluster Manager successfully, the cluster ownership transfer is complete.

If the cluster was transferred to a different organization, you can log into that organization to verify the update. The cluster now appears in the target Red Hat account’s clusters list, and has been removed from the previous Red Hat account’s clusters list.

It is recommended to update the pull secret to match the new owner once the transfer is complete. For more information about updating the pull secret, see Updating the global pull secret when transferring cluster ownership.

With the Red Hat OpenShift Cluster Manager, you can manage your clusters and monitor them for potential issues. The Status column in the Clusters list reports each cluster’s state so you can monitor your clusters at a glance.

The cluster status is shown in the Clusters list in OpenShift Cluster Manager. Normally, a cluster shows a status of Ready, however, there are other possible cluster statuses.

Red Hat Insights Advisor for OpenShift Container Platform allows you to assess and monitor the health of your OpenShift Container Platform clusters from the Red Hat Hybrid Cloud Console.

Insights Advisor highlights service availability, fault tolerance, performance, and security risks for your OpenShift Container Platform clusters based on Red Hat recommendations, so that you can avoid potential problems or solve problems quickly without unplanned downtime.

Recommendations include information about detected issues, including risk level, affected clusters, and steps for resolution where applicable.

To use Insights Advisor, your cluster must be registered to OpenShift Cluster Manager. To register a disconnected cluster, see Registering OpenShift Container Platform clusters to OpenShift Cluster Manager.

OpenShift Cluster Manager allows you to manage your clusters and monitor them for potential issues. The Status column in the Clusters list reports each cluster’s state so you can monitor your clusters at a glance.

An OpenShift Container Platform cluster can be shown as Stale in OpenShift Cluster Manager even if it is running and functioning normally. However, when a cluster status becomes Stale, you can no longer view internal information about the cluster in the OpenShift Cluster Manager Monitoring tab, including any alerts firing, cluster operators and resource usage.

In most cases, a cluster reports a Stale status because the telemeter-client cannot contact the Red Hat Telemetry endpoints. Telemetry enables the cluster to communicate with OpenShift Cluster Manager. If a cluster is reporting a Stale status, you can restore it to Ready and resume monitoring cluster health with the steps in this section.

After completing these steps, if you can view the cluster in OpenShift Cluster Manager but the status is still Stale, occasionally this may be because the cluster is owned by an inactive user in your Red Hat organization. If this is the case, you can restore the cluster to Ready by transferring cluster ownership to an active user in your organization.

You can revoke offline tokens in case you no longer need them or if you have reached the token limit.

All refresh tokens will stop working immediately after you remove access, but existing access tokens (which are cached by ocm and rosa commands) might take up to 15 minutes to expire.

Refresh the page afterwards to generate a new token.