I run a small k8s cluster and found myself running the same set of `kubectl` commands frequently to execute my troubleshooting decision tree! That's why I created the Kubernetes Runtime Scanner (KRS) - a pro-active, rule-based health assessment.

Why KRS?

- Automated Health Checks: Quick assessments of nodes, pods, and services (and others)

- Log Aggregation: Extracts and organizes relevant error logs.

- Resource Snapshots: View resource states at a glance.

- Open-Source & Extensible: let me know your troubleshooting workflow and I can try to incorporate it as pro-active checks!

I'm eager for feedback and collaboration. Try KRS, suggest features, or dive into the code. Your insights will make KRS an invaluable tool for every k8s user!

Here is a quick start guide on how to run a scan and get a report with about ~150 checks in a few minutes:

docker run -it -p 8888:8888 --user root unskript/awesome-runbooks:latest

CONTAINER_ID=`docker ps | tail -1 | awk '{print $1}'`; docker cp <KUBECONFIG.YAML> $CONTAINER_ID:/tmp/kubeconfig.yaml

docker exec -it $CONTAINER_ID bash

unskript-ctl.sh -cc -k8s /tmp/kubeconfig.yaml; unskript-ctl.sh -rc k8s