Free tool · ☸️ Kubernetes manifest generator
From image torunning on the cluster.
The manifests reviewers expect — probes, limits, non-root, rolling updates, TLS ingress — generated from the five things that actually vary.
Expects an NGINX ingress controller and cert-manager ClusterIssuer "letsencrypt-prod"; adjust names if different.
What it checks
Everything we would look at first on a client call.
Free, no sign-up, no email gate. If the report shows red, the fix is written next to it — and we are one click away if you would rather we did it.
- Deployment with RollingUpdate, probes, limits, security context
- Service + Ingress with TLS
- Optional HPA at 70% CPU
- kubectl commands and secret pattern
FAQ
Common questions
Where do secrets go?
In a Secret created from .env (command shown), referenced with envFrom — never in the manifest.
k3s or managed?
k3s/RKE2 on Proxmox for on-prem; EKS/AKS/GKE in cloud. The YAML is the same.