Closed danielpacak closed 2 years ago
@danielpacak Thats because of a bug in a new feature weve added. But anyways, by your question I understand you run kube-hunter with --log error. A better practice that will also solve this issue is running with --log none. This way even if we have some error internally with kube-hunter it will not mess up the report output
Got it. Thanks for the hint. We'll update the log level appropriately.
What happened
Integrated KH with Starboard so it runs with JSON output format as K8s pod. Then we parse the logs. I realised that in v0.5.2 parsing JSON output fails due to stack trace added by KH before the actual JSON content:
Expected behavior
Error or valid JSON output. Not both. Otherwise it's hard to determine whether KH failed or succeeded.
I did not bump into such issue with previous v0.4.1