diff options
| author | Paul Buetow <paul@buetow.org> | 2026-01-08 20:20:43 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-01-08 20:20:43 +0200 |
| commit | 8b22e5268fe4cad58584e2da36957cff1d0ce01c (patch) | |
| tree | 9fb0f20254b6d4b99e2d5beaaa173abd29ed329a /frontends/scripts/dns-failover.ksh | |
| parent | 806986a77f8e0fa8c2d9a5e9905e557000766ef0 (diff) | |
Disable kube-proxy and kube-scheduler monitoring for k3s
K3s embeds kube-proxy and kube-scheduler functionality into the main
k3s server process, unlike standard Kubernetes where they run as
separate components.
This change disables monitoring for these components to prevent
false-positive critical alerts:
- KubeProxyDown
- KubeSchedulerDown
These alerts were firing because kube-prometheus-stack expects
standard Kubernetes architecture with separate kube-proxy and
kube-scheduler pods/processes.
Cluster info:
- Running k3s v1.32.6+k3s1
- 3 control-plane nodes (r0, r1, r2)
- Components embedded in k3s binary
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Diffstat (limited to 'frontends/scripts/dns-failover.ksh')
0 files changed, 0 insertions, 0 deletions