What your cross-zone and internet traffic costs, per workload.
An eBPF agent on each node counts bytes between pods, zones and the internet, and Kubeadapt prices the traffic per workload. No sidecars, no pod restarts.
CEL · query language
Query your network
like a database.
Filter flows with CEL, the expression language Kubernetes uses in ValidatingAdmissionPolicy and CRD validation rules.
Filter by
Cross-zone and internet traffic
Traffic between zones and to the internet is billed per GB.
On AWS, cross-zone traffic costs $0.01/GB in each direction, and internet egress up to $0.09/GB. Traffic inside a zone is free. Below: one example cluster’s traffic for 30 days, by source and destination zone.
Top cross-zone talkers
Which workloads send traffic across zones.
Workloads ranked by cross-zone cost, with the zone most of their traffic goes to. What to change, if anything, is your call.
Example data · last 30 days · AWS transfer rates
Architecture
One agent per node. No sidecars.
A service mesh needs a proxy in every pod. Kubeadapt runs one eBPF agent per node and counts bytes per connection, so you get cost per flow without touching your pods. It records addresses, ports, byte counts, DNS names, TLS SNI and HTTP method, route and status. It never records payload bodies.
12 pods, 12 proxies
12 pods, 1 agent on the node
Requires the network agent kubeadapt-k8s-pulse, installed with the same Helm chart (--set kubeadapt-k8s-pulse.enabled=true). The DaemonSet runs privileged, with hostNetwork and hostPID, as root with a read-only root filesystem. Prices: AWS today. GCP and Azure: not yet.
Early access
Try it on your own clusters.
Early access is by request. Book a call and we will walk you through it. Cost monitoring, rightsizing and the rest of Kubeadapt are available today.