Commit Graph
11 Commits
Author SHA1 Message Date
Виталий ЧефановandClaude Opus 5.5 8b8fe341d5 v0.7.2: empty traffic window no longer blanks the map
The flows API sent "edges": null for a window without connections (a nil
Go slice); the frontend iterated it and renderMap threw after the new
breadcrumbs were drawn, so the previous namespace stayed on screen under
the new name. The API now sends empty lists, fetchFlows guards against
null, and a failed draw reports itself in the status bar.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 22:18:28 +03:00
Vitaliy ChefanovandClaude Opus 5.5 1df5d3559a v0.7.1: render alert rules on DKP without operator-prometheus-crd
helm_lib_prometheus_rules only renders when "operator-prometheus-crd" is
an enabled module; on DKP 1.76 that module doesn't exist (the CRDs come
with operator-prometheus), so the two alerts were silently dropped on a
live install. Gate on the PrometheusRule API instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 21:47:20 +03:00
Vitaliy ChefanovandClaude Opus 5.5 1bd2006125 bundle: ship changelog.yaml; keep version.json out of the Helm release
Both were warnings from `dmt lint remote` on the published bundle.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 21:30:44 +03:00
Vitaliy ChefanovandClaude Opus 5.5 d6558c3d44 Makefile: build into a local registry, publish only final artifacts
werf keeps every stage in --repo, base images included; pushing
Deckhouse's builder/golang-alpine (762 MB layer) to Gitea over a home
uplink timed out. Stages now live in a local registry:2 and publish
crane-copies the app image, bundle and release, keeping digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 21:27:31 +03:00
Vitaliy ChefanovandClaude Opus 5.5 18869e8bfc Makefile: keep only the base images this module uses
.werf/stages/base-images.yaml defines a werf image for every key of
base_images.yml, and Deckhouse's published file has ~1200 keys; a full
build started pulling and storing all of them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23 21:23:40 +03:00
Vitaliy ChefanovandClaude Opus 5.5 4518393ce1 Package cluster-map as a Deckhouse module
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>
2026-09-23 21:17:52 +03:00
Vitaliy ChefanovandClaude Opus 5.5 41f9b47556 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>
2026-09-23 20:26:05 +03:00
Vitaliy ChefanovandClaude Opus 5.5 6ead0a0d6d Collect Hubble traffic continuously; graph from informer caches
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>
2026-09-23 20:23:20 +03:00
Vitaliy ChefanovandClaude Opus 5.5 cf84e9976f UI rework: inventory tree, compact cards, live Hubble traffic
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>
2026-09-23 19:50:53 +03:00
Виталий ЧефановandClaude Sonnet 5 2ac0ddb6ba Add pod logs by click: /api/pods + /api/logs endpoints
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>
2026-09-23 18:56:50 +03:00
fanchji 8f9c650960 initial: graph backend (client-go) + cytoscape.js topology frontend
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.
2026-09-23 17:40:44 +03:00