Controller-runtime Cache Secrets That Prevent API Server Crashes
The post demystifies how controller-runtime serves reads from an in‑memory cache and sends writes straight to the API server, eliminating costly API calls but introducing memory and consistency pitfalls. It shows why poorly scoped List calls can explode memory usage and how proper indexing keeps controllers lightweight. Understanding this model prevents hidden O(N) scans and API‑server overload.