Gracefully fail unexpected Stream() calls
What does this MR do?
Makes the random failures of k8s integration job (like the one tracked at #26716 (closed)) to fail gracefuly. With logrus log level additionally changed to Debug, it should show in details what is happening and - hopefully - explain why these random failures exist.
Why was this MR needed?
The integration_k8s is recently failing randomly almost every day. With the merge train pipelines and pipeline must succeeds setting that we're using in the Runner project, it brings a lot of frustration.
This MR aims to give use more data. It will definitely not fix the randomly failing test. But with the new data (printed by all the logs and not hidden by panic caused by unexpected mock calls) we should be able to say why they are happening.
What's the best way to test this MR?
What are the relevant issue numbers?
Edited by Tomasz Maczukin