monitoring/alloy: drop cosmetic calico-typha 'Endpoints deprecated' warning
calico-typha (~342 lines/hr across 3 pods) still WATCHes the core v1 Endpoints API, so the apiserver returns the 'v1 Endpoints is deprecated in v1.33+' client-go warning, which typha logs. Per KEP-4974 the v1 Endpoints API will essentially never be removed (clients keep working indefinitely), and even the latest Calico still watches Endpoints (projectcalico/calico#11540) so a CNI upgrade would not fix it. Pure cosmetic noise. Targeted Alloy stage.drop (calico-system ns, exact deprecation message), mirroring the mailserver drop. Real calico warnings/errors kept; reversible. Validated with alloy fmt (exit 0). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
4b13be6d48
commit
7c12fbba95
1 changed files with 14 additions and 0 deletions
|
|
@ -149,6 +149,20 @@ alloy:
|
|||
}
|
||||
}
|
||||
|
||||
// Drop the cosmetic k8s deprecation warning calico-typha emits because
|
||||
// it still WATCHes the core v1 Endpoints API (~342 lines/hr across 3
|
||||
// typha pods). The v1 Endpoints API will essentially never be removed
|
||||
// (KEP-4974), so this is pure log noise — Calico is healthy and no
|
||||
// Calico release has moved typha's watch to EndpointSlice. Real
|
||||
// calico-system warnings/errors are KEPT. Reversible — delete to ship.
|
||||
stage.match {
|
||||
selector = `{namespace="calico-system"}`
|
||||
stage.drop {
|
||||
expression = `.*v1 Endpoints is deprecated in v1\.33\+; use discovery\.k8s\.io/v1 EndpointSlice.*`
|
||||
drop_counter_reason = "calico_endpoints_deprecation_warning"
|
||||
}
|
||||
}
|
||||
|
||||
stage.static_labels {
|
||||
values = {
|
||||
cluster = "default",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue