Container Licensing Non Compliance Means All Cores Charged.

How containers are licensed.

Containerized IBM software, including Cloud Paks, is licensed by Virtual Processor Core, or VPC. Since Passport Advantage v11, sub-capacity reporting through the IBM License Metric Tool applies to VPC metered products too, and manual counting is no longer permitted. The question is no longer how many cores a workload uses on average, but how many it is entitled to consume and whether you can prove it.

The all cores rule.

The detail that drives the largest container findings is simple to state and expensive to ignore. Where container or Cloud Pak deployments are out of compliance, IBM can charge for all of the cores in the cluster, not only the cores the eligible workload was using. A noncompliant deployment on a large worker pool is therefore measured against the entire pool.

Why estates drift out of compliance.

Clusters are built to scale and reschedule automatically, which is exactly what pulls them past their licensed position:

• Namespaces and components that outlive the project that created them
• Worker pools that grow well past their original sizing
• Metering not configured for the VPC metered products actually running
• Reports that exist but cannot be produced for the audited period

None of these is over deployment in the ordinary sense. They are reporting failures, and the all cores rule converts a reporting failure into a capacity sized bill.

What actually holds up.

An all cores finding is a claim, not a verdict. Where metering evidence, cluster topology, and retained reports support a sub-capacity count, that count can be defended. The work is reconstructing the consumed position period by period rather than letting the cluster ceiling stand in for it. For the structured defense, see our sub-capacity defense work and the foundations in Cloud Pak licensing and the VPC metric.

What this means under audit.

The all cores rule is the single most expensive container finding. Treat metering and report retention as compliance assets, and never accept a cluster sized count without testing whether the consumed VPC position can be evidenced.