KubeadaptDocsBack to site
Sign inStart free
DocsAPI ReferenceCLI
  • Introduction
  • Getting Started
  • Capabilities
    • Overview
    • Agent Configuration
    • eBPF Agent
    • Auto-Upgrade
Docs homev1ConfigurationEbpf Agent

Configuration

eBPF Agent

View source

Configuration reference for the Kubeadapt eBPF agent. Captures pod-to-pod network traffic for cross-AZ and egress cost visibility.


The eBPF agent runs as a DaemonSet on every node. It captures pod-to-pod network traffic and provides visibility into cross-AZ and egress data transfer.

Note

The eBPF agent collects pod-to-pod traffic metrics today. Full network cost attribution requires cloud provider pricing integration (starting with AWS), which is on the roadmap. Until then, you won't see network costs in the Kubeadapt UI. You can start collecting cross-AZ traffic data now so that when pricing integration ships, your historical data is already in place. Track the status on the roadmap.

Enable It

The eBPF agent is disabled by default. Enable it through the parent kubeadapt chart:

yaml
ebpf-agent:
  enabled: true

Or at install time:

bash
helm install kubeadapt kubeadapt/kubeadapt \
  --namespace kubeadapt \
  --create-namespace \
  --set agent.config.token="<your-token>" \
  --set ebpf-agent.enabled=true

Prerequisites

  • Linux nodes only with kernel 5.8 or later
  • Privileged container access (the DaemonSet runs as privileged)
  • hostNetwork: true and hostPID: true must be allowed by your pod security policy or admission controller
Warning

If your cluster uses a restrictive PodSecurityPolicy, OPA Gatekeeper, or Kyverno policy that blocks privileged containers, you need to create an exception for the kubeadapt namespace before enabling the eBPF agent.

Check Your Kernel Version

bash
kubectl get nodes -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.nodeInfo.kernelVersion}{"\n"}{end}'

All nodes must be running kernel 5.8+. Older kernels will fail to load the BPF programs.

Resources

yaml
1ebpf-agent:
2  resources:
3    requests:
4      cpu: 100m
5      memory: 128Mi
6    limits:
7      cpu: 500m
8      memory: 384Mi

If you see OOMKilled pods, increase the memory limit.

Scheduling

ValueTypeDefaultDescription
tolerationslist[]Pod tolerations.
nodeSelectorobject{}Node selector constraints.
affinityobject{}Pod affinity rules.
topologySpreadConstraintslist[]Topology spread constraints.
Tip

For complete network visibility, the eBPF agent should run on every node. Add a broad toleration so it is not excluded from tainted nodes.

Full Values Reference

The sections above cover what you need for enabling and scheduling the eBPF agent. For other configurations, see the full values.yaml.

PreviousAgent ConfigurationConfigurationNextAuto-UpgradeConfiguration

On this page

  • Enable It
  • Prerequisites
  • Check Your Kernel Version
  • Resources
  • Scheduling
  • Full Values Reference
Edit this page
Kubeadapt

Kubernetes FinOps platform. Cost visibility, rightsizing, and capacity planning that pays for itself in 30 days.

Product

  • Cost Monitoring
  • Cost Attribution
  • Workload Rightsizing
  • Recommendations
  • Smart Alerting
  • Best Practices
  • Network Cross-AZ

Resources

  • Documentation
  • Status Page
  • Feature Requests

Company

  • About Us
  • Security
  • Careers
  • Contact

© 2026 Kubeadapt. All rights reserved.

PrivacyTermsSecurity