OpenShift Container Platform cluster subscription settings

To ensure that you receive the correct level of support for your OpenShift Container Platform clusters, configure your cluster subscription settings in OpenShift Cluster Manager to align with the values for your Red Hat subscription.

For OpenShift Dedicated clusters, no further subscription configuration is needed after choosing your subscription type. OpenShift Dedicated clusters are automatically subscribed to Red Hat subscriptions and come with Premium-level support.

Note

To find more details about your subscriptions, view your Subscriptions Inventory in the Red Hat Customer Portal.

The following options are available for OpenShift Container Platform clusters:

Table 1. Subscription settings
Subscription setting Options Summary More information

Subscription type
  • Annual: Fixed capacity subscription from Red Hat
  • On-Demand: Flexible usage billed through the Red Hat Marketplace

What type of subscription are you using for this cluster?

Contact Red Hat Sales to enable On-Demand subscriptions from the Red Hat Marketplace for OpenShift Container Platform clusters.

Service level agreement (SLA)
  • Premium
  • Standard
  • Self-Support 60-day evaluation

How is this cluster supported?

The hours of coverage, support ticket response times, and other terms that are defined by the Service Level Agreement (SLA). See Production Support Terms of Service.

Support type
  • Red Hat support (L1-L3)
  • Partner support (L3)

Which team do you contact for primary support?

If you purchased the subscription through Red Hat, select L1-L3.

Cluster usage
  • Production
  • Development/Test
  • Disaster Recovery

How do you intend to use this cluster?

Describe the purpose of the cluster - for example, running production workloads or testing internal development projects.

Subscription units
  • Cores/vCPUs
  • Sockets

How is usage measured for your subscription?

Define how the cluster will consume the purchased Red Hat subscriptions.

Number of compute cores

A value between 1-999

How many compute cores does your cluster use?

NOTE: Configuration is only necessary on disconnected clusters.

This defines the number of physical cores used by your cluster. This excludes control plane nodes and nodes that do not use RHCOS. See OpenShift Container Platform compute core values for disconnected clusters for more details.

Subscription usage for OpenShift Container Platform
Copy link

The subscriptions service tracks OpenShift Container Platform usage as cluster size on physical and virtual systems. Cluster size is the sum of subscribed nodes that run workloads.

The subscriptions service tracks Red Hat OpenShift Container Platform usage in physical CPU cores or sockets for clusters and aggregates this data into an account view.

Subscriptions are used based on a 1 physical core or 2 vCPU core rate.

As an example, the subscription Red Hat OpenShift Container Platform, Standard/Premium (64 Cores or 128 vCPUs) supports an environment using either of these measurements:

  • 64 physical cores
  • 32 physical cores and 64 vCPUs

Both configurations are counted the same. This information can be viewed in the Cores field of the subscriptions service usage record, linked in Additional resources.

OpenShift Container Platform compute core values for disconnected clusters
Copy link

OpenShift Container Platform subscriptions are measured by physical cores and vCPUs or sockets, depending on your subscription terms.

Note

It is only necessary to configure the number of compute cores in OpenShift Cluster Manager for disconnected clusters.

In most cases, when configuring the Number of compute cores on your OpenShift Container Platform clusters, enter the number of compute cores and vCPUs or sockets included in your Red Hat subscription. Exclude any control plane nodes. This applies to all clusters using Red Hat Enterprise Linux CoreOS (RHCOS) as an operating system.

However, usage is not calculated against your OpenShift Container Platform subscription if your clusters have no worker nodes, or if the nodes use Red Hat Enterprise Linux only instead of RHCOS. In this case, enter a value of 1 for Number of compute cores for these nodes.

To confirm the unit of measurement used by your subscription and other details, log in to the Red Hat Subscription Management area in the Red Hat Customer Portal, linked in Additional resources.

Note

You cannot log in to your Red Hat account with your email unless your email is your Red Hat login. For more information, see Finding your login, linked in Additional resources.

View CPU information for your cluster
Copy link

You can use the oc CLI to find your cluster's CPU information, and then add it to OpenShift Cluster Manager so the subscriptions service can track your worker node usage.

Before you begin
Copy link

  • An OpenShift Container Platform cluster
  • Cluster administrator permissions
  • The OpenShift Container Platform oc CLI tool

Procedure
Copy link

  1. Log in to your cluster, replacing <username> and <api_server_url> with your values: 
    $ oc login -u <username> --server=<api_server_url>

    The command prompts you for your password.

  2. List the nodes in your cluster and their roles: 
    $ oc get nodes -o wide
  3. Get the CPU information for each node: 
    $ oc describe nodes | grep -E 'Name:|InternalIP:|cpu:'

    Add up the cpu values for your worker nodes.

  4. On the Clusters page, click the name of your cluster.
    The cluster Overview tab opens.
  5. From the Actions menu, select Edit subscription settings.
  6. In the Number of compute cores (excluding control plane nodes) field, enter your total, and then click Save.
    Note

    If you run OpenShift on a hypervisor and your compute core count looks wrong, check that your hypervisor groups vCPUs the same way your subscription does. For details, see the Red Hat Knowledgebase article The number of cores for my OpenShift cluster on console.redhat.com is higher than what it should be.

Results
Copy link

The subscriptions service in the Red Hat Hybrid Cloud Console now uses your core count, which you can use to plan subscription renewals or purchases.