Azure Red Hat OpenShift
Azure Red Hat OpenShift — commitment brief
Data sourced: March 2026. Verify current figures at the Azure Pricing Calculator.
Coverage summary
Azure Red Hat OpenShift (ARO) has two separate cost layers, each with its own commitment instrument. The OpenShift software (license) meter on worker nodes can be committed via a Red Hat OpenShift software plan reservation. The underlying Azure VM compute for worker and control-plane nodes can be committed separately via Azure Reserved VM Instances or the Azure Compute Savings Plan. The two instruments must be purchased independently — neither covers both layers. Software plan reservations for ARO are final: cancellations and exchanges are not allowed. Monthly payment is not available (upfront only).
What is covered (software plan): The Red Hat OpenShift license meter generated by worker nodes, applied per VM size/vCPU band. Instance size flexibility applies within the same VM series group.
What is covered (VM-level commitments): Azure VM compute costs for worker and control-plane nodes, via Reserved VM Instances (up to ~72% at 3-yr) or the Azure Compute Savings Plan (up to ~65% at 3-yr).
What is not covered: Control-plane node OpenShift license meters (only worker nodes generate the software meter), storage (Azure Disks, Azure Files), networking/egress, data transfer. Neither commitment covers both the software and compute layers simultaneously.
Azure Hybrid Benefit
Partially applicable. AHB does not apply to the Red Hat OpenShift software license — that is governed by the Red Hat licensing agreement. However, AHB applies to the underlying Azure VM compute layer for Windows Server licenses if running Windows workloads on OpenShift Virtualization. Linux-based cluster nodes follow standard Linux VM licensing.
SKU / tier coverage
OpenShift software meter — D-series workers
✅ Yes (software plan)
❌ No
varies
~50–70% (software layer)
Upfront payment only; no cancellations/exchanges
OpenShift software meter — E-series workers
✅ Yes (software plan)
❌ No
varies
~50–70% (software layer)
Instance size flexibility within series group
Worker/Control-plane VMs — D-series
✅ Yes (VM RI)
✅ Yes (Compute SP)
~36–40%
~55–65%
VM compute layer; reserved independently
Worker/Control-plane VMs — E-series
✅ Yes (VM RI)
✅ Yes (Compute SP)
~36–40%
~55–65%
Storage (Azure Disks, Azure Files)
❌ No
❌ No
—
—
Reserve separately via disk/file reservations
Reservation vs. Compute Savings Plan (VM layer)
Reserved VM Instance (VM layer): Scoped to a specific VM family and region. Highest discount on the compute layer (up to ~72% at 3-yr). Best for stable worker node VM families.
Compute Savings Plan (VM layer): Flexible across VM families, regions, and other compute services. Up to ~65% at 3-yr. Better when cluster VM sizes or regions may change.
Regional availability
Azure Red Hat OpenShift is available in a subset of commercial Azure regions — not all Azure regions support ARO cluster deployment. OpenShift software plan reservations and VM-level Reserved VM Instances are available wherever ARO is deployed. The Azure Compute Savings Plan applies globally across all commercial regions for the VM compute layer.
Notable exclusions: Azure Government and Azure China regions are not supported for ARO or its reservations. Software plan reservations are only available in regions where ARO worker node deployment is supported.
⚠️ Availability varies by SKU and region. Always verify in the Azure portal or via the Azure Retail Pricing API before purchasing.
Archera
Azure Red Hat OpenShift (VM compute layer) is within Archera's commitment management scope. Archera can automate Reserved VM Instance purchase for ARO worker node VM families, monitor utilization, and wrap commitments in a GRI/GSP.
Sources
⚠️ Software plan reservations are final — no cancellations or exchanges. Monthly payment is not available. Discount percentages vary by VM size and region. Always verify with the Azure Pricing Calculator.
Last updated
Was this helpful?