k8s-cluster-review
Cluster review
Review a running cluster for what drifted in after it was deployed: settings that do
not break anything today, but hurt during the next drain, load spike or incident, or
cost money for nothing. Read only. Run the investigation commands freely. Never
change, scale, label or delete anything yourself: every fix here is a proposed fix for
the user or the owner of the object. Never read Secrets, and never exec into a pod;
the review needs neither.
Manifest linters (kube-linter, Polaris, kube-score) check what is in a repository. This review checks what ended up in the cluster. If the user already has output from one of those tools, use it as extra evidence; never install them.
The commands use placeholders: my-namespace, my-app, my-node. Replace them with
the real names. Cluster-wide checks need read access to nodes, PersistentVolumes and
the RBAC objects, which the built-in view role leaves out. If a command is forbidden,
do not treat it as "nothing found": put the check in the report's Skipped section with
the command for the user to run.