Update master.yaml

Fix 1.1.23 to check *if* --service-account-lookup argument is set and if so then if it's equal to true

Fix title of 1.4.21 from 644 to 600 according to cis benchmark

Adds master node detection - thanks @Kuqd! 

The root command will run node checks and if possible master checks.
I've also added some Makefile targets to improve local testing and improve the documentation.

Update openshift executable config

Clean up OCP benchmark config.

add new config files from the new CIS Kubernetes Benchmark

The OCP benchmarks uses configs for only binary component variable names.
This commit cleans up the OCP config by removing all configuration
except those component binaries required to run kube-bench on OCP
installations and adds missing ones.

Fix the start from 1.11 to 1.13 and adding changes from pull #227, and pull #228.

replace with the new node.yaml file

replace with the new master.yaml file

replace with the new config.yaml file

Fix issues with checks for kubelet configuration files

Only find flags on the process we really want

There are checks for the kubeconfig for both kubelet and proxy which
the current kube-bench implementation does not check for properly.
kube-bench checks the wrong files.

This PR adds support for variable substitution for all the config file
types are that should be checked in the CIS benchmarks.

This PR also fixes a buggy in CIS 1.3.0 check 2.2.9, which checks for
ownership of the kubelet config file /var/lib/kubelet/config.yaml but
recommends changing ownership of kubelet kubeconfig file
/etc/kubernetes/kubelet.conf as remediation.

This fix applies to only checks for kubernetes versions 1.8 and 1.11.
See https://github.com/aquasecurity/kube-bench/pull/208.

there is a new update at CIS_Kubernetes_Benchmark_v1.4.0 for Kubernetes 1.13

search for the kubelet binary when it is not in the path

Bugfix: Logging warning instead of printing

Made all the warnings to be logged and not printed, so when using the json flag the output will be only in json format.

fix #217

OCP benchmarks and configs

Tests could easily be marked "skip" because the user doesn't want to run them in their environment, and in this common case the set of tests will be non-nil

Signed-off-by: Weston Steimel <weston.steimel@gmail.com>

Type skip and not scored checks

If a check is marked with type "skip", it will be marked as Info.

Support scored property:
If a check is not scored and is not marked with type skip, it will be marked as Warn.