Container Sprawl and the All Cores in the Cluster Penalty

When IBM software runs in containers without compliant license metering, IBM does not charge for the cores the workload used. It charges for every core in the cluster. That is the single most punishing default in modern IBM licensing.

Why containers change the math

Container platforms schedule workloads dynamically. A pod can land on any node, move between nodes, and scale out across the cluster on demand. That flexibility is the point, but it also means IBM cannot assume a workload stays put. Without an approved way to measure where the software actually ran, IBM treats the entire cluster as licensable capacity.

The all cores default

For container and Cloud Pak deployments, the rule is direct: if the deployment is not metered by an approved license service, IBM charges for all cores in the cluster, not just the cores the IBM software consumed. A handful of small pods on a large OpenShift cluster can convert into a finding measured against every worker node present.

• License Service not deployed or not collecting for the namespace
• Metering data missing for the periods the workload ran
• New nodes added to the cluster without coverage
• IBM software running outside the entitled topology

How sprawl makes it worse

Cluster sprawl multiplies the exposure. As teams add nodes for unrelated workloads, the cluster grows, and so does the core count IBM can claim if metering lapses for even one reporting period. The penalty is not proportional to your IBM usage, it is proportional to the size of the infrastructure the IBM software happened to live on.

How to contain it

Deploy and validate the IBM License Service for every cluster that runs Cloud Pak or other container metered IBM software, confirm it is collecting continuously, and retain the reports. Where a finding already cites all cores in the cluster, the contest is whether compliant metering data exists for the period, and whether the cluster boundary IBM drew is the right one. The difference between an all cores claim and an actual usage claim is frequently the entire dispute.