# What Kubernetes misconfigurations have caused you real production problems? — retained record

> Retained reddit record from reddit:devops.

Canonical: https://highsignal.app/data/records/2b9d0eafc89634f5

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:devops)  published 2026-08-18 07:32 ingested 2026-08-19 06:47

[original source ↗](https://www.reddit.com/r/devops/comments/1vribl5/what_kubernetes_misconfigurations_have_caused_you/)

## retained text



```
<!-- SC_OFF --><div class="md"><p>After working with Kubernetes in production, I've noticed that some of the most annoying incidents aren't caused by obvious failures. They're often caused by small configuration decisions that look perfectly reasonable during review.</p> <p>Things like:</p> <ul> <li>missing resource requests/limits</li> <li>incorrect probes</li> <li>overly permissive RBAC</li> <li>missing PodDisruptionBudgets</li> <li>unsafe container configuration</li> <li>incorrect readiness behaviour</li> <li>services without appropriate timeouts</li> <li>configuration drift between environments</li> </ul> <p>I'm curious what the DevOps community has actually encountered in production.</p> <p><strong>What's one Kubernetes configuration mistake that caused you a real incident?</strong></p> <p>I'd especially like to hear about the less obvious ones that aren't caught by the usual linters.</p> </div><!-- SC_ON --> &#32; submitted by &#32; <a href="https://www.reddit.com/user/nerd3n"> /u/nerd3n </a> <br /> <span><a href="https://www.reddit.com/r/devops/comments/1vribl5/what_kubernetes_misconfigurations_have_caused_you/">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/devops/comments/1vribl5/what_kubernetes_misconfigurations_have_caused_you/">[comments]</a></span>
```



document fetched 2026-08-19 06:47 · canonical https://reddit.com/r/devops/comments/1vribl5/what_kubernetes_misconfigurations_have_caused_you
