CI mode about kube-no-trouble HOT 3 CLOSED

This was closed via #49, -e flag will now make kubent to return non-zero (200) exit code in case issues are found. Also Use in CI section was added to the docs mentioning this new flag and some other examples. Finally, we've added tests to make sure the error-code behaviour is as expected and will stay so. 🚀 . Thanks @estahn and @Djiit for you input on the topic! 👍

(This is now only in master, but I expect to cut a new release probably early next week).

from kube-no-trouble.

Thanks @estahn, this is good suggestion. I was thinking about this earlier, and initially decided to reserve non-zero return codes to actual failure - ie. if there's an error.

It should be fairly simple to do basic test in CI, as "log" outputs go to stderr, and only findings go to stdout. Following should give you the non-zero if there are any findings:

test -z "$(kubent)"

Would that cover your use case?

There's also json output mode (-o json) that should allow for amore convenient further processing of results.

Alternatively, what behaviour would you expect in terms of differentiating between error and deprecated resources found?

from kube-no-trouble.

FWIW, Trivy has this exit-code parameter (https://github.com/aquasecurity/trivy#specify-exit-code). The default is 0, but you can tell Trivy to return 1 (or whatever) if it makes sense. If a real error is encountered, this parameter is ignored.

from kube-no-trouble.