version: 2.3.11
If configmapcontroller gets redeployed, it appears to immediately restart all the deployments that are annotated for update-on-change, even if the ConfigMaps have not been updated.
Perhaps it needs to persist the last check time so that can be referenced by the new deployment.