Spring Cleaning 2026 Day 6: kvestigate (investigate k*)

Kvestigate - Investigate Kubernetes Clusters Ever find yourself given access to a piece of garbage kubernetes cluster and you need need to audit it to figure out what the hell is going on? Say hello to kvestigate your kubernetes investigation and auditing toolkit with the ability to even run ad-hoc workloads beyond the reach of the kubernetes scheduler allocator substrate system by just doing shit on the hosts themselves like computers are supposed to do. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Language Files Lines Code Comments Blanks ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Python 141 34192 28551 1381 4260 TOML 3 72 57 8 7 YAML 23 1059 718 257 84 ───────────────────────────────────────────────────────────────────────────────── Markdown 18 3983 0 3083 900 |- BASH 13 500 288 141 71 |- Python 6 177 132 27 18 |- YAML 3 218 187 11 20 (Total) 4878 607 3262 1009…