text: Title: Kubelet failing to update pod with updated configmap in large cluster
  Body: Ref https://github.com/kubernetes/kubernetes/issues/47344#issuecomment-312349193
  
  This is in regard to the following e2e tests checking configmap(/secret/projected) update being reflected in pod volume:
  [k8s.io] ConfigMap updates should be reflected in volume [Conformance] [Volume]
  [k8s.io] ConfigMap optional updates should be reflected in volume [Conformance] [Volume]
  (similar ones for secret,projected)
  
  This one's the last correctness test (on 5k-node cluster) that needs fixing :)
  The logs for the run are here - http://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-enormous-cluster/13/
  We are using n1-standard-1 nodes running all default daemons.
  
  cc @kubernetes/sig-node-bugs @kubernetes/sig-scalability-misc @dchen1107 