← Back to guidesGuide

Monitor controller-runtime without melting the Kubernetes API server

A practical workflow to catch LIST storms, stale caches, reconcile queues, and control-plane alerts before your operator becomes the incident. A generous little gift from automation.

Learn how to monitor Kubernetes controllers built with controller-runtime using Prometheus, workqueue metrics, API server signals, promtool rules, and canary validation.

Created: August 27, 2026

Published: August 27, 2026

Estimated time45 min

LevelAdvanced

Before you startPrometheus scraping the API server and custom controllers

PlatformsLinux / Docker

WhatsApp X LinkedIn

Docker

Validate rules locally with synthetic fixtures before changing the shared Prometheus server.

Dockerrules/*.yamltests/*.yaml

Run promtool in a container

docker run --rm -v $PWD:/work -w /work prom/prometheus:latest promtool test rules tests/controller-runtime-cache-pressure.test.yaml

Check syntax

docker run --rm -v $PWD:/work -w /work prom/prometheus:latest promtool check rules rules/controller-runtime-cache-pressure.yaml

Also available inMonitorizar controller-runtime sin fundir el API server de Kubernetes

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.