Reducing disk i/o of geneva logging #4561
Merged
+17
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue this PR addresses:
Epic: https://issues.redhat.com/browse/ARO-23137
Card: https://issues.redhat.com/browse/ARO-23139
Control plane nodes can experience disk pressure from logging/monitoring components becoming a noisy neighbor to Etcd.
This change set tunes Geneva logging (fluent-bit + mdsd) to minimize disk usage and reduce OOM risk, while keeping container log collection behavior unchanged.
What this PR does / why we need it:
This PR tunes Geneva logging (fluent-bit + mdsd) to reduce control plane disk usage and better match real resource consumption. It disables inotify watching only for kube-apiserver audit log tailing (container logs remain inotify-based).
Test plan for issue:
Is there any documentation that needs to be updated for this PR?
No
How do you know this will function as expected in production?
Test plan with production cluster documented TBD (link)