Restricted OpenShift entitlement for IBM Cloud Paks

Depending on where you obtain Red Hat® OpenShift® Container Platform from, it can have implications on what you can deploy on it.

Red Hat OpenShift Container Platform clusters are entitled by cores, not by individual nodes. You can stack entitlements of different types together to ensure that all of the cores in a cluster have a valid entitlement according to the terms and conditions for that entitlement.

If you obtain Red Hat OpenShift Container Platform as part of a bundle with your IBM Cloud Pak®, your Red Hat® OpenShift® Container Platform cores are restricted cores. They can only be used in support of your IBM Cloud® Paks.

Important: Whether or not your Red Hat OpenShift Container Platform cores are restricted or not, you can still take full advantage of all of the features that are included in Red Hat OpenShift Container Platform, for example, but not limited to, OpenShift Pipelines.

If you obtain Red Hat OpenShift Container Platform independent of your IBM Cloud Pak, such as purchasing it directly through Red Hat®, your Red Hat® OpenShift® Container Platform cores are unrestricted cores. They can be used to support your IBM Cloud Paks and any other application or monitoring agent.

The following diagrams illustrate what you can deploy on which cores depending on your entitlement type.

Permitted deployment

You can run IBM Cloud Paks and bundled applications on restricted cores. Any application that is not bundled with your IBM Cloud Paks (for example Dynatrace monitor) requires additional unrestricted cores. Any applications that do not run on Red Hat OpenShift Container Platform are not affected.

Permitted deployments

Not permitted deployment

You cannot run any non IBM Cloud Pak or non IBM Cloud Pak bundled application or monitoring agent on restricted cores that are bundled with IBM Cloud Paks.

Not permitted deployment