Joshua Hoblitt 0763f91f93 operator: silence 'cm is handled by another watcher' DEBUG messages ...

I guesstimate that around 50% of the operator log volume when set to log
level `DEBUG` are messages about cm's which aren't relevant to rook.

E.g.:

```
2022-09-16 23:03:05.430839 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "ingress-controller-leader" cm is handled by another watcher
2022-09-16 23:03:05.643255 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "fleet-agent-lock" cm is handled by another watcher
2022-09-16 23:03:05.799526 D | ceph-cluster-controller: hot-plug cm watcher: only reconcile on hot plug cm changes, this "cattle-controllers" cm is handled by another watcher
```

Yes, it is `DEBUG` and noise is expected. However, there is no message
about checking the status of the cm's rook actually needs to watch and
these messages don't seem very useful. I have been resorting to piping
the operators logs through `| grep -v 'hot-plug cm watcher'` to cut down
the noise.

Signed-off-by: Joshua Hoblitt <josh@hoblitt.com>

2022-09-16 16:23:19 -07:00

..

ceph

operator: silence 'cm is handled by another watcher' DEBUG messages

2022-09-16 16:23:19 -07:00

discover

test: use T.Setenv to set env vars in tests

2022-07-15 23:07:19 +08:00

k8sutil

csi: customize plugin volumes and volumemounts

2022-09-16 09:57:37 +05:30

test

nfs: add support for running SSSD as a sidecar

2022-08-11 14:59:23 -06:00