Core-pair = 2 physical cores or 4 vCPUs
Catalog row in Vendor License Rules · Cited
- Kind
- Counting
- Statement
- Self-managed Red Hat OpenShift subscription guide: Core-pair “is defined as 2 physical cores or as 4 virtual central processing units (vCPUs). On a bare-metal machine, it always refers to the physical core, regardless of any hyperthreading or symmetric multithreading technology. If hyperthreading is turned on, then 2 physical cores that present as 4 vCPU are still counted as a single core-pair. For hyperscaler deployments, e.g. AWS, Azure, and GCP, 4 vCPU are always considered a single core-pair.” Guide subscription type label: “Core-pair (2 cores or 4vCPUs).” Product Appendix 1 (February 2026) Table 2 prints Virtual Node capacity “2 Cores or 4 vCPUs” for Red Hat OpenShift Container Platform / Platform Plus — binding Appendix token aligned with the guide. Guide is educational and does not supersede Appendix 1. Red Hat publishes no 2-vCPU = 1-socket conversion for Cloud Access or RHEL Socket-pair.
- Applies when
- Entitling self-managed OpenShift compute with Core-pair / Core-based Virtual Node capacity across clusters (on-prem, virtual, or hyperscaler).
- Applies to
- Self-managed OpenShift (OpenShift Kubernetes Engine, OpenShift Container Platform, OpenShift Platform Plus) Core-pair / “2 Cores or 4 vCPUs” Virtual Node capacity. Not OpenShift Virtualization Engine bare-metal-only. Not RHEL Socket-pair.
- Aliases
- Core-pair packing; 2 cores or 4 vCPUs; hyperscaler 4 vCPU = 1 core-pair