v0.8.2: no false problems for redirecting Ingresses and deleted pods
Found on the live cluster: d8-monitoring/grafana-v10 routes prometheus.<domain> to a Service that does not exist, but a snippet redirects every such request, so the backend is never used. And a verification pod created and deleted by a backup check kept a warning badge on its namespace for 30 minutes after it was gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
1025c40561
commit
b01f884530
@@ -1,3 +1,7 @@
|
||||
v0.8.2:
|
||||
fixes:
|
||||
- An Ingress that answers with a redirect (redirect annotations, or rewrite ... permanent / return 30x in a snippet) is not reported for a backend Service that does not exist; Deckhouse's prometheus Ingress does exactly that.
|
||||
- Warning events about a pod that no longer exists are listed for information and no longer badge the card.
|
||||
v0.8.1:
|
||||
fixes:
|
||||
- "Actions: the DexAuthenticator is annotated allow-access-to-kubernetes, so the user's token carries the kubernetes audience and the API server accepts it. In v0.8.0 the token lacked that audience, the API server rejected it and actions were unavailable."
|
||||
|
||||
Reference in New Issue
Block a user