K8s Agent
The NudgeBee Agent is a lightweight software component that runs inside your Kubernetes cluster. It collects data about workloads, performance, cost, and security, and sends it to the NudgeBee server — feeding the Semantic Knowledge Graph that powers NudgeBee's Cloud-Ops Intelligence. You need to install an agent in every cluster that you want NudgeBee to monitor. The agent supports AWS, Azure, GCP, and on-premises Kubernetes environments.
Both Cloud SaaS and self-hosted users need to install the agent. This is how NudgeBee gets visibility into your Kubernetes clusters, regardless of your deployment model.
If you connected a cloud account (AWS, Azure, or GCP), NudgeBee can auto-discover your Kubernetes clusters. You may still need to install the agent for deep monitoring, but cluster discovery happens automatically.
What You Will Find in This Section
- Installation — Step-by-step guide to deploy the agent using Helm, including prerequisites and system requirements. Typically takes 5 –10 minutes per cluster.
- Helm Values — Complete reference for agent Helm chart configuration values.
- Upgrade — How to upgrade an existing agent to a newer version.
- Kubernetes Provider Setup — Provider-specific instructions for GKE, AKS, and other managed Kubernetes services.
- Logging Integration — Connect log sources (ELK, Loki, SignalFx, etc.) to the agent.
- Tracing Integration — Connect tracing backends (ClickHouse, GCP) for distributed tracing.
- Proxy Agent — Deploy agents through a proxy for restricted or air-gapped environments.
- Local Setup — Run NudgeBee locally for development and testing.
- On-Prem Setup — Additional configuration for air-gapped or on-premises environments.
Architecture
The NudgeBee Agent runs within your Kubernetes cluster. The main component is the Runner, which acts as a central controller — it collects data from various components and communicates with the NudgeBee Server over HTTP and WebSocket.

Components
Event Watcher (Forwarder) - Watch for K8s events and Forward to Runner
- Monitors Kubernetes events using the Kubernetes API server.
- Filters and processes events based on predefined criteria.
- Forwards relevant events to the Runner component.
Node Agent - Network Metrics Collection using eBPF
The Node Agent is responsible for collecting network metrics on each Kubernetes node using eBPF (Extended Berkeley Packet Filter) and publishing them to Prometheus for further analysis.
-
eBPF Probe
- Attaches eBPF probes to key networking events, such as packet transmissions and receptions.
- Captures relevant metrics, including latency, throughput, and error rates.
-
Metric Publisher
- Aggregates collected metrics.
- Publishes metrics to Prometheus for centralized monitoring.
- Detects Application Errors (Logs and API Errors) and publishes these metrics to Prometheus.
Runner - Discovery and Communication with NudgeBee Server
The Runner component facilitates the discovery of Kubernetes cluster workloads and communicates with the NudgeBee server for workload synchronization.
-
Workload Discovery
- Uses the Kubernetes API to discover running workloads within the cluster.
- Periodically updates the list of workloads.
-
Communication with NudgeBee
- Establishes a secure connection with the NudgeBee server.
- Sends information about discovered workloads to the NudgeBee server for further processing.
CostModel - Cost Collection
NudgeBee uses OpenCost for calculating cost metrics for Pods/Workloads etc.
Recommendation Jobs
NudgeBee runs the following container Images on a scheduled basis as K8s Jobs for generating specific recommendations.
Security Recommendation NudgeBee Currently uses Trivy for Generating Docker Image Vulnerability related security Recommendations
Usage Recommendation NudgeBee Currently uses Krr for Generating Usage related Recommendations
Best Practices Recommendation NudgeBee Currently uses Popeye for Generating Best Practices related Recommendations
Prometheus (Or VictoriaMetrics) - Metrics Collection and alerting