Cluster charge reversed on a Cloud Pak audit.

The client ran an IBM Cloud Pak on an OpenShift cluster that also hosted unrelated workloads. During an audit, IBM identified a container compliance gap and applied the container rule that bites hardest: where a Cloud Pak deployment is non-compliant, IBM charges for every core in the cluster, not only the cores running the licensed software. The opening claim counted the entire cluster against the Cloud Pak entitlement.

The exposure was not driven by over-deployment of the IBM product. It was driven by the cluster boundary. The licensed workload sat well within entitlement, but the charge swept in cores that never touched the Cloud Pak. Left unchallenged, the methodology, not the usage, would have set the number.

The cluster wide charge was reversed back to the licensed workload. By proving the VPC count and the entitlement boundary, the defense moved the basis of the claim from the whole cluster to the cores that actually ran the Cloud Pak. The corrected container reporting posture was carried into the settlement so the same gap could not reopen at the next lookback.