Take the security of your Kubernetes environments to the next level with our data scan addon, guaranteeing proactive monitoring and unrivalled protection of your clusters, for total peace of mind in the container world.
Report Bug
·
Request Feature
For each of your EndPoint, the following keys are mandatory:
- "rules": this refers to the set of rules files you want to apply to this environment.
- "prefix": the prefix is the particle to be placed in front of the environment variables to be quoted here.
The following keys are recommended to ensure better readability when re-reading the configuration:
- "name": the name refers to the environment concerned by one or more keywords.
- "description": the description helps to clarify the name and avoid any possible confusion about the environment concerned.
Example config for 2 environments:
You need to get and give the path to the access config to your kubernetes:
KUBECONFIG=./Path/to/your/configThe config file looks something like this:
apiVersion: v1
clusters:
- cluster:
certificate-authority-data:
server:
name:
contexts:
- context:
cluster:
user:
name:
current-context:
kind: Config
preferences: {}
users:
- name:
user:
client-certificate-data:
client-key-data:
token: To provide access to your config file for kexa docker version, you can do a volume mount. Putting this file directly in the same folder as your default.json is the simplest solution. The path to this file would then be :"./config/[Name of your config file]"