IBM License Service for Container Reporting

In a containerized estate, ILMT is not the tool that proves your sub-capacity position. The IBM License Service, deployed into the OpenShift or Kubernetes cluster, is what measures VPC consumption for Cloud Pak and container deployed software. When it is missing or incomplete, IBM has a rule ready: charge all the cores in the cluster. The reporting tool is the defense.

What the License Service does

The IBM License Service runs inside the cluster and measures the virtual processor cores consumed by licensed containers over time, producing the audit ready reports that VPC metered products rely on. For container and Cloud Pak deployments it plays the role ILMT plays on traditional hosts: it is the evidence that you consumed less than the full cluster. Without that evidence for a period, there is no measured number to stand on, only the cluster total.

Why a gap is so expensive

Container non-compliance carries the harshest default in the IBM model. When the License Service is not deployed, not running continuously, or cannot produce reports for the lookback period, IBM charges for all cores in the cluster rather than the cores the licensed workload actually used. On a busy OpenShift cluster shared across many teams, the gap between consumed cores and total cluster cores can be an order of magnitude.

• Not deployed: no measured consumption, so the whole cluster is in scope
• Deployed late: the period before deployment defaults to full cluster charging
• Reporting gaps: any quarter without reports is treated as unmeasured
• Wrong scope: nodes the License Service cannot see are counted at full capacity

VPC and the Passport Advantage v11 shift

Since Passport Advantage v11, sub-capacity reporting and an approved tool apply to VPC metered products, and manual counting is no longer permitted. For containers this means the License Service is not optional bookkeeping, it is the mechanism that makes the VPC number defensible at all. Treating it as a deploy and forget component is how buyers arrive at an audit with months of unmeasured consumption.

How buyers defend it

The defensible posture starts with confirming the License Service is deployed across every node where licensed containers can schedule, running continuously, and exporting reports that are retained. Where a finding charges the full cluster, the counter is the License Service record showing the actual consumed VPC quarter by quarter, plus evidence that the deployment scope covered the workloads in question. We reconcile what was reported against what was deployed and rebuild the period the audit treated as unmeasured wherever the data supports it.