Add kube-bench dry run to script/validate #173
Merged
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.
Parent issue: rancher/cis-operator#227
This PR adds another layer of verification, to ensure that a given CIS benchmark is not faulty.
Let's say we introduce a typo in cis-1.7/master.yaml, (
tiype
instead oftype
), but yamllint didn't return any errors. Kube-bench can be run against the given benchmark (e.g cis-1.7), if any of the cis-1.7's files have a typo it won't run.kube-bench indicates which component (file) is faulty :
error setting up master controls: non-master controls file specified
Example of scenario:
YAMLLINT test 🟢
KUBE-BENCH dry-run 🔴