NetObserv Operator
NetObserv Operator is a Kubernetes operator for network observability based on eBPF (extended Berkeley Packet Filter) that captures network flow data from…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
68/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 49271 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 70no serious findings, 6 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 271
- Open issues
- 37
- Last commit
- 2026-11-05
- Latest release
- 2.0.2-community
- License
- Apache-2.0
- Activity
- declining
Checked 15 days ago - source: GitHub (netobserv/netobserv-operator)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Installing the operator Deploys into a Kubernetes cluster such as OpenShift or Kind via its Helm chart; the operator installs the eBPF flow agent, the Flowlogs pipeline, and the web console inside the cluster. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to install the operator for continuous network monitoring?
Install the operator for 24/7 network flows monitoring. The CLI is the separate option for on-demand monitoring and troubleshooting.
What does the operator developer local setup cover?
It covers environment preparation, infrastructure deployment, building and deploying the operator, and advanced workflows for testing component changes.
Is there an FAQ in the netobserv-operator repository?
Yes, the repository includes an FAQ file on the main branch.
Where are operator development changes contributed?
Contributions are made to the netobserv/netobserv-operator repository.
Answers sourced from deepwiki.com, github.com, github.com, netobserv.io
Community
No community discussions collected yet.