From df3577519cffe77350d4ef60945cc233bef9b97c Mon Sep 17 00:00:00 2001 From: Liz Rice Date: Thu, 30 May 2019 22:55:48 +0100 Subject: [PATCH] Document version-specific config files Values in the version-specific files override the main file --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 8eb2b98..ed8852d 100644 --- a/README.md +++ b/README.md @@ -131,6 +131,8 @@ kube-bench includes a set of test files for Red Hat's OpenShift hardening guide Kubernetes config and binary file locations and names can vary from installation to installation, so these are configurable in the `cfg/config.yaml` file. +Any settings in the version-specific config file `cfg//config.yaml` take precedence over settings in the main `cfg/config.yaml` file. + For each type of node (*master*, *node* or *federated*) there is a list of components, and for each component there is a set of binaries (*bins*) and config files (*confs*) that kube-bench will look for (in the order they are listed). If your installation uses a different binary name or config file location for a Kubernetes component, you can add it to `cfg/config.yaml`. * **bins** - If there is a *bins* list for a component, at least one of these binaries must be running. The tests will consider the parameters for the first binary in the list found to be running.