oc v3.6.170 operation_generator.go:609] MountVolume.SetUp succeeded for volume "kubernetes.io/configmap/a8a247f8-72fe-11e7-a49e-122631632f42-config-volume" (spec.Name: "config-volume") pod "a8a247f8-72fe-11e7-a49e-122631632f42" (UID: "a8a247f8-72fe-11e7-a49e-122631632f42"). operation_generator.go:609] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/a8a247f8-72fe-11e7-a49e-122631632f42-router-token-qxgtl" (spec.Name: "router-token-qxgtl") pod "a8a247f8-72fe-11e7-a49e-122631632f42" (UID: "a8a247f8-72fe-11e7-a49e-122631632f42"). operation_generator.go:609] MountVolume.SetUp succeeded for volume "kubernetes.io/secret/a8a247f8-72fe-11e7-a49e-122631632f42-server-certificate" (spec.Name: "server-certificate") pod "a8a247f8-72fe-11e7-a49e-122631632f42" (UID: "a8a247f8-72fe-11e7-a49e-122631632f42"). My node is running a single pod. Every ~2 minutes I see the 3 above log messages. These are all spam at V(2). I want to know about system state changes at V(2). Not useless spam over and over and over. On a busy node (150+ pods) this can easily add up to more than 4 messages per second of useless log spam. I wouldd like to see log message about state change in this area at V(2). If this message has any debug value please reduce them to at least V(4).
Somebody's done it for 1.7, I'll backport it to 3.6 https://github.com/kubernetes/kubernetes/pull/46367
If it's done in 3.7 just close the BZ