Contour · FinOps Profile

Contour Finops

FinOps shape for Contour - an Apache 2.0 / CNCF Incubating open-source project. There is no upstream Contour invoice. Operator FinOps cost is borne by the underlying Kubernetes platform (compute, network egress, observability) and any commercial Kubernetes-distribution support contract the operator chooses to layer on.

Contour Finops is the FinOps profile for Contour on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 3 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 Envoy, Ingress Controller, Kubernetes, Networking, and Open Source.

Category: Open Source Networking Pricing: Open Source (No Charge) Billing: N/A FOCUS v1.3
EnvoyIngress ControllerKubernetesNetworkingOpen SourceProxyFinOpsFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

FOCUS Columns

BillingCurrency
N/A
ChargeCategory
N/A
PricingCategory
Free
ProviderName
Project Contour
PublisherName
Project Contour Authors
ServiceCategory
Open Source Networking
ServiceName
Contour

Meters

contour_pods
Unit: pod-hour
Contour control-plane pods running in the cluster (compute time consumed, billed by the underlying Kubernetes platform)
envoy_pods
Unit: pod-hour
Envoy data-plane pods running as DaemonSet / Deployment under Contour
ingress_traffic
Unit: GB
HTTP / TLS ingress traffic processed by Envoy (drives load-balancer and egress charges on the underlying cloud)

Sources