Kubernetes Manifest Review Checklist
Check workloads for reliability and security.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review my Kubernetes manifests. Paste them with secrets removed: [MANIFESTS]. Cluster version and managed or self-hosted: [CLUSTER_INFO]. Workload type: [WORKLOAD_TYPE]. Check and report in a table: resource requests and limits, probes (liveness, readiness, startup), replicas and disruption budgets, rollout strategy, security context (non-root, read-only filesystem, dropped capabilities), network policies, service accounts and permissions, secrets handling, image tags, and pod anti-affinity or topology spread. For each finding give severity, a concrete patch in YAML, and how to verify with a command. Summarise the three issues most likely to cause an outage and the three most likely to cause a security problem. Say which findings depend on cluster version and need verification against current documentation. Add a section describing which of your recommendations are safe to apply directly and which need staged rollout because they could restart pods or break connectivity. Include a command list for verifying each fix after applying it, and a policy suggestion to prevent the same issue recurring, such as an admission control rule in warn mode first. Add a worked example of two findings in full: a deployment without readiness probes and a container running as root. For each show the issue, why it matters in terms of an outage or a security consequence, the YAML patch as a short fragment, the verification command concept, the risk of applying it (for example, pods restarting), and the safe rollout step. Add a severity rubric with definitions of critical, high, medium and low that I can edit, and a table of recommended defaults for requests and limits that you derive only from the usage figures I provide, marked as starting points. Finish with a policy-in-warn-mode proposal and a two-week review of violations before enforcement. Close with a short list of settings that look harmless but commonly cause outages in practice, such as missing disruption budgets or probes that restart healthy pods, with how to confirm each.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.