Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 1. Red Hat OpenShift Cluster Manager

Red Hat OpenShift Cluster Manager is a managed service where you can install, modify, operate, and upgrade your Red Hat OpenShift clusters. This service allows you to work with all of your organization’s clusters from a single dashboard.

OpenShift Cluster Manager guides you to install OpenShift Container Platform, Red Hat OpenShift Service on AWS (classic architecture), Red Hat OpenShift Service on AWS, and OpenShift Dedicated clusters. It is also responsible for both OpenShift Container Platform clusters after self-installation as well as your Red Hat OpenShift Service on AWS (classic architecture), Red Hat OpenShift Service on AWS, and OpenShift Dedicated clusters.

You can use OpenShift Cluster Manager to do the following actions:

  • Create clusters
  • View cluster details and metrics
  • Manage your clusters with tasks such as scaling, changing node labels, networking, authentication
  • Manage access control
  • Monitor clusters
  • Schedule upgrades
  • Transferring cluster ownership

For more information about OpenShift Cluster Manager, see the entire OpenShift Cluster Manager documentation.

1.1. Accessing Red Hat OpenShift Cluster Manager
Copy link

You can access OpenShift Cluster Manager with your configured OpenShift account.

Prerequisites

  • You have an account that is part of an OpenShift organization.
  • If you are creating a cluster, your organization has a specified quota.

Procedure

1.2. General actions
Copy link

On the top right of the cluster page, there are some actions that a user can perform on the entire cluster:

  • Open console launches a web console so that the cluster owner can issue commands to the cluster.
  • Actions drop-down menu allows the cluster owner to rename the display name of the cluster, edit the machine pools, and delete the cluster. You may also transfer the cluster’s ownership to another user.
  • Refresh icon forces a refresh of the cluster.

1.3. Cluster tabs
Copy link

Selecting an active, installed cluster shows tabs associated with that cluster. The following tabs display after the cluster’s installation completes:

  • Overview
  • Access control
  • Add-ons
  • Cluster history
  • Networking
  • Machine pools
  • Support
  • Settings

1.3.1. Overview tab
Copy link

The Overview tab provides information about how the cluster was configured:

  • Cluster ID is the unique identification for the created cluster. This ID can be used when issuing commands to the cluster from the command line.
  • Domain prefix is the prefix that is used throughout the cluster. The default value is the cluster’s name.
  • Type shows the type of cluster, for example ROSA (classic), ROSA with HCP, or Dedicated.
  • Region is the server region.
  • Availability shows which type of availability zone that the cluster uses, either single or multizone.
  • Version is the OpenShift version that is installed on the cluster. If there is an update available, you can update from this field.
  • Created at shows the date and time that the cluster was created.
  • Owner identifies who created the cluster and has owner rights.
  • Delete Protection: <status> shows whether or not the cluster’s delete protection is enabled.
  • Status displays the current status of the cluster.
  • Total vCPU shows the total available virtual CPU for this cluster.
  • Total memory shows the total available memory for this cluster.
  • Infrastructure AWS account displays the AWS account that is responsible for cluster creation and maintenance.
  • Additional encryption field shows any applicable additional encryption options.
  • Nodes shows the actual and desired nodes on the cluster. These numbers might not match due to cluster scaling.
  • Cluster autoscaling field shows whether or not you have enabled autoscaling on the cluster.
  • Instance Metadata Service (IMDS) field shows your selected instance metadata service for the cluster.
  • Network field shows the address and prefixes for network connectivity.
  • OIDC configuration field shows the Open ID Connect configuration for the cluster.
  • Resource usage section of the tab displays the resources in use with a graph.
  • Advisor recommendations section gives insight in relation to security, performance, availability, and stability. This section requires the use of remote health functionality. See Using Insights to identify issues with the cluster in the Additional resources section.

1.3.2. Access control tab
Copy link

The Access control tab allows the cluster owner to set up an identity provider, grant elevated permissions, and grant roles to other users.

1.3.2.1. Identity providers
Copy link

You can create your cluster’s identity provider in this section. See the Additional resources for more information.

1.3.2.2. Cluster roles and acess
Copy link

You can create a dedicated-admins role for {product-short-name} clusters or cluster-admins role for Red Hat OpenShift Service on AWS classic architecture clusters.

Procedure

  1. Click the Add user button.
  2. Enter the ID of the user you want to grant cluster admin access.
  3. Select the appropriate group for your user. Either dedicated-admins for {product-short-name} clusters, or cluster-admins for ROSA (classic) clusters.

1.3.2.3. OCM roles and access
Copy link

Prerequisites

  • You must be the cluster owner or have the correct permissions to grant roles on the cluster.

Procedure

  1. Click the Grant role button.
  2. Enter the Red Hat account login for the user that you wish to grant a role on the cluster.

  3. Select the role from following options:

    • Cluster editor allows users or groups to manage or configure the cluster.
    • Cluster viewer allows users or groups to view cluster details only.
    • Cluster autoscaler editor allows users or groups to manage and configure the cluster autoscaler settings.
    • Identity provider editor allows users or groups to manage and configure the identity providers.
    • Machine pool editor allows users or groups to manage and configure the machine pools.
  4. Click the Grant role button on the dialog box.

1.3.2.4. Transfer ownership
Copy link

You can transfer your cluster to another user.

Note

Once you transfer cluster ownership, you lose access to the cluster.

Procedure

  1. Select Initiate transfer.
  2. Enter the user name, account ID, and organization ID of the user that you are transferring the cluster to.
  3. Select Initiate transfer.

1.3.3. Add-ons tab
Copy link

The Add-ons tab displays all of the optional add-ons that can be added to the cluster. Select the desired add-on, and then select Install below the description for the add-on that displays.

1.3.4. Cluster history tab
Copy link

The Cluster history tab shows every change to the cluster from creation onward for each version. You can specify date ranges for your cluster history and use filters to search based on the description of the notification, the severity of the notification, the type of notification, and which role logged it. You may download your cluster history as a JSON or CSV file.

1.3.5. Networking tab
Copy link

The Networking tab provides a control plane API endpoint as well as the default application router. Both the control plane API endpoint and the default application router can be made private by selecting the respective box below label. If applicable, you can also find your virtual private cloud (VPC) details on this tab.

Select the Edit application ingress button to edit the existing application ingress. You can change your application ingress to private or public by checking or unchecking the "Make router private" checkbox.

Important

For Security Token Service (STS) installations, these options cannot be changed. STS installations also do not allow you to change privacy nor allow you to add an additional router.

1.3.6. Machine pools tab
Copy link

The Machine pools tab allows the cluster owner to create new machine pools if there is enough available quota, or edit an existing machine pool.

Selecting the kebab > Edit option opens the "Edit machine pool" dialog. In this dialog, you can change the node count per availability zone, edit node labels and taints, and view any associated AWS security groups.

Select the Edit cluster autoscaling button to specify your autoscaling strategy.

1.3.7. Support tab
Copy link

In the Support tab, you can add notification contacts for individuals that should receive cluster notifications. The username or email address that you provide must relate to a user account in the Red Hat organization where the cluster is deployed. For the steps to add a notification contact, see Adding cluster notification contacts.

Also from this tab, you can open a support case to request technical support for your cluster.

1.3.8. Settings tab
Copy link

The Settings tab provides a few options for the cluster owner:

  • Monitoring, which is enabled by default, allows for reporting done on user-defined actions.
  • Update strategy allows you to determine if the cluster automatically updates on a certain day of the week at a specified time or if all updates are scheduled manually.
  • Node draining sets the duration that protected workloads are respected during updates. When this duration has passed, the node is forcibly removed.
  • Update status shows the current version and if there are any updates available.

1.4. Additional resources
Copy link

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat