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
+3
View File
@@ -1,3 +1,6 @@
v0.11.6:
fixes:
- Topology routing fallback is informational only when a Service has a Ready selected backend; missing backends still warn.
v0.11.4:
fixes:
- "Failed probes (Unhealthy events) of a pod that is ready now are listed for information: the pod's state already reports NotReady and restarts. Deckhouse answers /readyz with 500 while it works through its queue after a module change and tolerates ten minutes of it; that badged its card after every module release."