The OpenShift renewal and audit checklist

A Red Hat renewal or audit is a negotiation, and whoever brings the defensible number sets the anchor. Walk in reacting to Red Hat’s figure and you are arguing from behind. Walk in with your own evidence-backed position and the conversation changes. This is the buyer-side checklist for getting there.

Start before the window opens

Begin six to twelve months before the renewal date. Entitlement questions take time to resolve, and the worst time to discover an overage is the week the quote lands. If an audit notice has already arrived, the same steps apply — just compressed.

The checklist

• Inventory the entitlements. List every active subscription and the SKUs behind it, with the core-pairs each one grants.
• Inventory the consumption. Capture the cores your billable nodes actually run, per cluster and per node role.
• Resolve the offering. Separate self-managed from ROSA, ARO, and Dedicated — each is counted by its own rules.
• Reconcile per SKU. Compare entitled core-pairs against consumed core-pairs, applying rounding and offering rules, to get the net position.
• Account for peaks. If the cluster autoscales, know your high-water mark, not just today’s snapshot.
• Build the evidence. Tie every number to its source — subscription, SKU, node inventory — so the position holds up under scrutiny.

Negotiate from your number

With a reconciled position in hand, a renewal stops being a reaction. You know whether you are over- or under-licensed, by how much, and exactly why — which means you can true up only what is real, push back on what is not, and right-size before you re-sign.

How RenewalIntel makes the checklist automatic

Each step above is what RenewalIntel does continuously for Red Hat: it resolves SKUs and offerings, reconciles entitled against consumed core-pairs, prices the gap, and generates an evidence packet in which every value traces to its source. The defensible number is ready before the renewal letter is, not assembled in a panic after it arrives.