The YAML janitor problem: why Kubernetes dev environments always drift and how to fix it

A platform engineer at a 40 person startup told us he spent every Monday morning going through a backlog of "my environment is broken" tickets. He was not writing code. He was manually patching dev namespaces because someone had updated a ConfigMap in production and the dev copies had drifted again. "I'm basically a janitor for YAML," he said. He was not unusual. We heard the same story from team after team. Platform engineers spending 5 to 10 hours a week on dev environment tickets. Senior developers waiting half a day to get a working namespace before they could even start on a feature. Onboarding taking a week because the dev environment setup was a tribal knowledge document that was never quite right. Why the common approaches break down There are four ways most teams try to solve this. Each one has a predictable failure mode. Helm values per environment. A values-dev.yaml alongside values-prod.yaml is the most common starting point. It feels controlled because the files are in ver