Layout, build and templates follow deckhouse/modules-template; dmt lint
passes with no findings (Go files are excluded from the Flant-only
license-header rule, see .dmtlint.yaml).
- module.yaml, openapi schemas with Russian docs, lib-helm templates:
https modes, ingress class, publicDomainTemplate, node placement,
priority class, PSS-restricted security context, VPA, PDB, Ingress
plus Gateway API ListenerSet/HTTPRoute, DexAuthenticator.
- module-sdk hooks: hubble CA from d8-cni-cilium (public certificate
only), external_auth, copy_custom_certificate.
- The app moves to images/cluster-map/src and is split into packages;
traffic mode Continuous/OnDemand/Disabled and retention are module
settings; graceful shutdown; Prometheus metrics and two alerts;
frontend embedded, English and Russian, strict CSP.
- Built with werf on Deckhouse's published base images; Makefile
publishes the registry layout modules-actions uses.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
The ring buffer on each agent holds 4095 flows, ~10 s at the observed
~380 flows/s, so the 5/15/60 min windows were really showing the last
few seconds. A background follow stream now fills per-minute buckets
for the last hour, and counts are distinct connections (5-tuples)
instead of Hubble events, with opened (SYN) and dropped broken out.
/api/flows reports coveredSec so the UI can say how much of the window
the collector has seen since start.
/api/graph reads informer caches instead of listing every kind per
request (~0.9 s before). Pod-to-workload resolution for flows uses the
same cache. YAML view drops managedFields.
Frontend: traffic refreshes in place every 30 s without relayout; dash
animation rationed (12 fps, only highlighted edges in dense views,
paused after a minute idle) since each step redraws the whole element
layer, ~15 ms on a 200-element view.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Frontend rewritten around three panes. Inventory tree on the left
(namespaces by kind, or nodes by namespace) with search and keyboard
navigation replaces the namespace checkbox list. The map shows only the
selected namespace(s) or node: fixed-size cards inside namespace boxes,
laid out in two elk passes so a big namespace packs into rows instead of
one tall column; zoom is capped so the view no longer jumps. Details
panel has Overview / Links / YAML / Logs tabs. Light and dark themes.
Libraries are vendored, no CDN.
Backend: /api/flows reads recent flows from hubble-relay (TLS verified
with the hubble CA, no client cert needed) and aggregates them per
source/destination/port. Pods are resolved to workloads with the same
rules as the graph, since Hubble leaves Workloads empty on some flows.
Pods under non-native controllers (kruise DaemonSet, CNPG clusters,
bare Jobs, static pods) are now graph nodes too. Probes move to
/healthz: /api/graph was timing out the 1s probe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deployment/StatefulSet/DaemonSet/CronJob details now show a pod +
container picker with the pod's recent log tail (500 lines, no follow),
sitting alongside the existing raw-manifest view. Pod resolution reuses
buildGraph's ownerReferences-walking logic (ownerWorkloadID) so it stays
consistent with the schedules-on edges already shown on the graph.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Namespaces as compound parents, Deployment/StatefulSet/DaemonSet/CronJob
as workload nodes, Service/Ingress with edges derived from label-selector
matching and backend references, plus a physical-node layer via pod
placement. Click-through to live YAML manifest per node.