Controller-runtime cache protects the API server, but can hide memory bloat
The article explains that controller-runtime reads from a local in‑memory cache populated via list+watch, so reconciler reads are cheap and don’t hit the API server, preventing overload. However, this design can hide memory bloat, cause stale reads, and trigger O(n) scans if indexes are mis‑configured, leading to production surprises.