CRI-O · FinOps Profile

Cri O Finops

FinOps shape for CRI-O - an Apache 2.0 / CNCF Graduated open-source container runtime. There is no upstream invoice. Operator cost is borne by the underlying compute (node-hours), image storage, and image-pull egress on the hosting cluster.

Cri O Finops is the FinOps profile for CRI-O on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in N/A, on a n/a cycle, and pricing category open source (no charge).

The profile maps 7 FOCUS columns for cost-allocation reporting.

Tagged areas include CNCF, Container Runtime, Containers, CRI, and Kubernetes.

Category: Open Source Container Runtime Pricing: Open Source (No Charge) Billing: N/A FOCUS v1.3
CNCFContainer RuntimeContainersCRIKubernetesOCIOpen SourceFinOpsFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

FOCUS Columns

BillingCurrency
N/A
ChargeCategory
N/A
PricingCategory
Free
ProviderName
CRI-O Project
PublisherName
CRI-O Authors / CNCF
ServiceCategory
Open Source Container Runtime
ServiceName
CRI-O

Meters

container_runtime_hours
Unit: node-hour
Node-hours of CRI-O runtime time (proxied via underlying node billing on the cloud provider)
image_pulls
Unit: pull
Container image pull operations (drives upstream registry egress and any registry bandwidth charges)
image_storage
Unit: GB
Container image / layer storage on the node disk (drives node-disk capacity sizing)
container_starts
Unit: event
Container start events (operational metric from CRI-O Prometheus metrics)

Sources