k8s-review

Review Kubernetes manifests and Helm charts for production readiness and common failure modes.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill k8s-review-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-review
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/devops/skills/k8s-review
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill k8s-review-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Kubernetes misconfigurations like missing resource limits, broken probes, and unpinned image tags cause OOMKills, CrashLoopBackOffs, and downtime during node drains. This Skill audits manifests and Helm charts against a severity-ordered checklist so problems are caught before kubectl apply. ## Core Features & Use Cases - Severity-Ordered Review: Blockers (resources, probes, secrets, image tags, securityContext) first, then availability concerns (replicas, PodDisruptionBudgets, HPA, rolling updates), then config and networking (Ingress TLS, NetworkPolicy, RBAC). - Symptom-to-Cause Cheatsheet: Maps live cluster symptoms like CrashLoopBackOff, OOMKilled, Pending pods, and ImagePullBackOff to their most likely root causes and first diagnostic commands. - Runnable Verification: Provides kubectl dry-run, diff, QoS inspection, and rollout status commands, plus optional kube-score and kubeconform validation. - Use Case: Before merging a new Deployment, run the review to catch a missing memory limit and a liveness probe that checks the database, then apply the corrected YAML snippets provided in the findings table. ## Quick Start Review the Kubernetes manifests in ./manifests for production readiness and list blockers with corrected YAML.

Frequently Asked Questions about k8s-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Kubernetes manifests before deploying to production?▼

Review Kubernetes manifests in severity order: first check resource requests and limits, probe configuration, secret handling, pinned image tags, and securityContext, then availability items like replicas, PodDisruptionBudgets, and HPA. Validate with kubectl apply --dry-run=server and kubectl diff before applying.

How to fix CrashLoopBackOff and OOMKilled pods in Kubernetes?▼

For CrashLoopBackOff, run kubectl logs --previous to find missing env vars, secrets, or failed migrations. For OOMKilled (exit 137), compare the memory limit against actual usage from kubectl top pods, then raise the limit or fix the leak.

What is the difference between readiness and liveness probes?▼

A readinessProbe gates traffic and should check dependencies like databases, while a livenessProbe should only detect a wedged process. If liveness checks the database, a brief DB blip restarts the whole fleet and turns a degradation into an outage.

Does HPA work without resource requests set?▼

No, the HorizontalPodAutoscaler requires CPU or memory requests to be set because it scales on utilization relative to requests. Also avoid combining HPA with a fixed replicas field in the same Deployment, since it conflicts with GitOps tools like ArgoCD and Flux.

Why are my Kubernetes config changes not applying?▼

ConfigMap updates do not restart pods automatically, so mounted config stays stale. Add a checksum annotation to the pod template or use a reloader so ConfigMap changes trigger a rollout.