subPath ConfigMap Mounts Don't Hot-Reload: Silent Drift in Kubernetes

A Pipelock instance running in a Kubernetes cluster watched its config file for hours while four edits to the underlying ConfigMap landed in etcd. The dashboards showed updates. The pod showed an old config. The tests that exercised the new config kept failing for reasons that made no sense. The problem is not Pipelock. The problem is subPath . Mount a ConfigMap key as a single file with subPath , and kubelet stops propagating updates to that mount. The behavior is documented but easy to miss, a