Filter infra traffic at the Hubble agents

Host-originated flows, remote-node, cilium health and DNS :53 were ~74%
of the non-reply events on a 12k-event sample and none of them map to a
workload card; streaming them all kept hubble-relay at ~400m CPU. They
are now blacklisted in the GetFlows request, so agents drop them before
the relay. The UI's "Служебный" toggle had nothing left to show and is
gone; the legend says what isn't collected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Vitaliy Chefanov
2026-09-23 20:26:05 +03:00
co-authored by Claude Opus 5.5
parent 6ead0a0d6d
commit 41f9b47556
4 changed files with 23 additions and 11 deletions
+8 -1
View File
@@ -10,7 +10,8 @@ Topology map of the Project Chimera Deckhouse cluster.
→ workload by label selector); dashed animated arrows are real traffic
from Hubble Relay over the chosen window (5 min / 15 min / 1 h), red when
Cilium dropped some of it. Peers from other namespaces are drawn as
dashed "ghost" cards. Traffic refreshes in place every 30 s without
dashed "ghost" cards. Kubelet probes, DNS, cilium health and node-to-node
traffic are not collected (see Backend). Traffic refreshes in place every 30 s without
relayout; peers that would need new cards wait for "Обновить".
- **Right**: details for the selected object — overview, links (config and
traffic, clickable), live YAML, pod logs.
@@ -37,6 +38,12 @@ produces several events. `new` = opened by TCP SYN inside the window,
only knows what it has seen since; `coveredSec` says how much of the
window that is.
Infra traffic is filtered at the agents (`infraFilters` in `flows.go`):
host-originated flows (kubelet probes, hostNetwork pods), remote-node,
cilium health and DNS :53. On a 12k-event sample they were ~74% of
non-reply events, none of them attach to a workload card, and streaming
them cost hubble-relay ~400m CPU.
| Endpoint | What |
|---|---|
| `/api/graph` | nodes + config edges + pod placement |