Description of problem: must-gather collects too much data. This is unnecessary large and doesn't help troubleshooting - actually the sheer size makes the investigation harder. Also this increases transfer time. Most notably, kubelet logs are unnecessarily big because there is no bound to how much history we collect (= we get everything it's available on the node!) Version-Release number of selected component (if applicable): 4.7.0 How reproducible: always Steps to Reproduce: 1. run must-gather against a cluster 2. 3. Actual results: must-gather takes too much time to collect data; the collected data is unnecessarily (= no clear need) large. Most notably kubelet logs are too big. Expected results: must-gather collects a bounded amount of kubelet logs (not everything) Additional info: Unclear how much is enough. Unless a clear reason is given to go back in time, each amount is heuristically determined.
to reproduce: 1. run must-gather (repeatedly) 2. verify it still collects kubelet logs 3. verify the kubelet logs cover the last 8hours (approximatively)