fix: classify healthy topology routing fallback as information

This commit is contained in:
Виталий Чефанов
2026-10-27 10:06:00 +03:00
parent e6dafc746c
commit a1d5fe98ae
5 changed files with 73 additions and 3 deletions
+2
View File
@@ -31,6 +31,8 @@ A card with a problem carries a badge: yellow `!` for a warning, red `!` for an
Information-level entries (a cordoned node, a single ordinary warning) are listed and never badge a card. Problems are recomputed on every map request and the open page refreshes them every minute.
Ordinary restart history expires after 30 minutes regardless of lifetime restart count; repeated OOM kills retain the 24-hour window. `TopologyAwareHintsDisabled` is informational only for a Service with a Ready selected backend: Kubernetes uses cluster-wide routing when hints cannot be allocated. Missing backends still produce warnings. No cluster routing configuration is changed.
## Vulnerabilities
With operator-trivy installed, a card whose images have CRITICAL CVEs shows a red shield with their number in the bottom-right corner. The details panel lists every CRITICAL and HIGH CVE of the workload's images: the packages it hits, the installed version and the version that fixes it, with a link to the advisory. A CVE counts once per card, however many packages and containers it is found in. Vulnerabilities are shown apart from problems: nearly every image has some, and a badge on each card would hide what is actually broken.