results-controller

README

results-controller CLI usage

The tool expects a set of input information to run:

• kubeconfig: kubeconfig file. default: in-cluster configuration, Fallback $HOME/.kube/config
• log-level: logging level (debug, info...)
• resync: default synchronization period. (seconds)

These values can be provided as flags to the command:

As flags to the command

For eg, the following command can be used to run the cli in debug mode with a custom kubeconfig file.

$ results-controller  --log-level debug --kubeconfig kubeconfig
DEBU[0000] log level configured                          log-level=debug
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted
DEBU[0000] Node event omitted

resync is optional and will get default 60 value:

prune subcommand

The prune subcommand is in charge of cleaning up older checkresult objects in the cluster. It will maintain only those checkresult whose spec.completedAt field is between the range specified in the keep flag and the current date.

results-controller prune --log-level debug --kubeconfig kubeconfig --keep 24h