Machine Health Check controller has excessive trace logging #9418
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What steps did you take and what happened?
When log level 3 or higher on the CAPI controller manager and a machine health check is configured, the machine health check controller logs it's reconciliation for each target. However, it accumulates the targets it reconciles in the logger values, which results in extremely long log statements. In larger clusters (> 100 ndoes) this becomes excessive and breaks the ability to effectively debug or read the logs for the machine health checks.
An example log message from one of our clusters (this is only 1 log line, but it's 13k chars!):
What did you expect to happen?
The machine health check controller reconciliation should only annotate it's logger values with the target it's currently examining the health check for, not an accumulation of all previous machines.
Cluster API version
1.5.1
Kubernetes version
1.24.14
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.
The text was updated successfully, but these errors were encountered: