Bare Metal Node
Catalog row in Vendor License Metrics · Cited
- Unit
- Other
- Aliases
- bare-metal node; Bare Metal
- Definition
- Appendix 1 names OpenShift Bare Metal Node SKUs as Physical Node with Socket-pair capacity bands. The self-managed OpenShift subscription guide (202601) treats a bare-metal node as one physical server regardless of the number of CPU sockets or cores; a subscription cannot span servers.
- Counting rules
- Purchase one Bare Metal Node subscription per physical server. Capacity is Socket-pair with up to 64 Cores, or up to 128 Cores for subscriptions purchased after 1 January 2025 based on the new MSRP (Exhibit 1.B Note 2), including Virtual Nodes hosted on OpenShift Virtualization on the Physical Node. OpenShift Virtualization is supported only when OpenShift is installed on the bare metal server and is not installed within a virtual machine. Distinct from Physical Node as a general Appendix 1 Unit; distinct from Core-pair Virtual Node SKUs. There is no conversion from Bare Metal Node to Core-pair.
- Floors / minimums
- Socket-pair with up to 64 Cores; after 1 January 2025 MSRP, Socket-pair with up to 128 Cores (Note 2). OpenShift Virtualization Engine: Physical Node, Socket-pair with up to 128 Cores. Device Edge: 1 Socket with up to 32 Cores.
- Applies to products (more)
- Red Hat OpenShift AI
- Red Hat OpenShift Container Platform
- Red Hat OpenShift Kubernetes Engine
- Red Hat OpenShift Platform Plus
- Red Hat OpenShift Platform Plus (without OpenShift Container Platform)
- Red Hat OpenShift Platform Plus with OpenShift Data Foundation Advanced
- Red Hat OpenShift Virtualization Engine
- Applies to editions
- Bare Metal Node
- Related metrics