Diagnose Kubernetes API WATCH/LIST pressure before blaming etcd

Practical golden signals to separate real API server latency, watch storms, and storage pressure.

An actionable guide for detecting Kubernetes API WATCH/LIST pressure by combining API server, etcd, Prometheus, and client validation before timeouts spread.

Created: June 23, 2026

Published: June 23, 2026

Estimated time35 min

LevelAdvanced

Before you startRead access to kube-apiserver and etcd metrics

PlatformsLinux

WhatsApp X LinkedIn

Linux

Linux terminal workflow using kubectl, curl, jq, and PromQL against Prometheus.

kubectlcurljqPrometheus access

Check API server health

kubectl get --raw /readyz?verbose

Extract key metrics

kubectl get --raw /metrics | egrep 'apiserver_request_duration_seconds|apiserver_current_inflight_requests|apiserver_storage_objects|apiserver_watch_events_total'

Also available inDiagnosticar presión de WATCH/LIST en Kubernetes API antes de culpar a etcd

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.