Vulnerabilities: VulnerabilityReports from operator-trivy are cached
(trimmed to the fields shown) and mapped to cards through the scanned
object in their labels. A card shows a red shield with its CRITICAL CVE
count; the details list CRITICAL and HIGH CVEs with packages, installed
and fixed versions and the advisory link, one row per CVE and image.
Counted per CVE, not per package: openssh's six subpackages had made one
CVE count six times. Kept apart from problems on purpose: on the live
cluster 22 cards have some, which would bury the "is it working" badges.
Fixes, both found on the live cluster, where they made all five current
"problems":
- a Warning event's count is cumulative since its first occurrence; four
dex-authenticators on xeon had 38-51 probe failures over two days (one
an hour, pods never left Ready) and were badged as a burst. The count
is now scaled to the part of the event's lifetime the window covers.
- upmeter's smoke-mini services and pods are its synthetic test, moved
between nodes on purpose (NoEndpoints, FailedMount while moving).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Problems: cards, namespace and node boxes and the tree carry a yellow or
red badge, computed on the server from object state (crash loops, image
pulls, pending and unschedulable pods, readiness older than 2 minutes, a
stuck rollout, a failed CronJob run, Services without endpoints,
Ingresses to missing Services, node conditions), recent Warning events
(notable reasons at once, others after five repeats) and Deckhouse
ClusterAlerts mapped by their labels. A Problems panel lists them all.
Checked against the live cluster: upmeter's synthetic probe pods and
ingress-nginx's fakeservice Ingresses are excluded, they fail on purpose.
Actions: restart, scale, run a CronJob now, suspend/resume, delete a
pod, cordon/uncordon. They run with the viewer's bearer token from the
DexAuthenticator (sendAuthorizationHeader), buttons follow a
SelfSubjectAccessReview, the service account stays read-only. Cross-site
writes are refused by Sec-Fetch-Site/Origin/content type. Scale retries
on conflict: right after a restart a single Get+Update got 409.
Load (metrics.k8s.io against requests/limits/allocatable, per-pod table)
and an Events tab. Cards are locked until the padlock is opened; the map
exports to PNG; the page refreshes badges every minute in place.
Performance, measured on the live cluster:
- layout of big views 3-4x faster: equal-size cards with no edges are
laid out on the grid ELK would produce (same sizes, checked against
ELK on a frozen node view), skipping ~8 ms per ELK call;
- hubble-relay gets ~20% fewer flows: the to-overlay copy of pod-to-pod
traffic is dropped at the agents; 331/331 directions unchanged;
- static files carry ETags, a reload revalidates instead of pulling
~2 MB of vendored scripts.
KUBECONFIG is honoured for running the binary on a workstation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>