All Tools View Categories About Contact Privacy

Kubernetes Best-Practices Checker

Audit pasted manifests for missing limits, requests, probes and root containers.

Runs entirely in your browser - nothing is uploaded and no cluster connection is made.
Your report will appear here.

About Kubernetes Best-Practices Checker

The Best-Practices Checker audits pasted Kubernetes manifests for the most common production mistakes: containers without CPU/memory limits or requests, without liveness or readiness probes, and containers that run as root.

Paste one or more manifests (Pod, Deployment, StatefulSet, DaemonSet or Job). The tool walks every container and reports each issue with a severity tag so you can prioritise fixes.

Nothing is uploaded. The YAML is parsed and analysed entirely in your browser.

Features

  • Limits & requests - flags missing CPU/memory limits and requests.
  • Probes - flags missing liveness/readiness probes.
  • Root check - flags containers running as root.
  • Multi-doc - analyse several manifests at once.
  • Copy / Download / Print - export the report.

How to Use

  1. Paste your manifest(s) into the YAML box.
  2. Click Check.
  3. Review the findings and fix each container.

Examples

Example 1 - missing limits. A container with no resources block is flagged HIGH.

Example 2 - root. A container without runAsNonRoot is flagged HIGH.

Example 3 - clean. A fully configured container reports no violations.

Benefits

  • Fast audit - find mistakes before they reach production.
  • Severity tags - focus on HIGH first.
  • Private - runs fully in the browser.
  • Exportable - copy, download or print the report.

Frequently Asked Questions

What does this checker look for?
It scans each container for missing CPU/memory limits and requests, missing livenessProbe and readinessProbe, and containers configured to run as root.
Which manifests are supported?
Pods and workload controllers (Deployment, StatefulSet, DaemonSet, Job) - anything with a spec.template.spec.containers or spec.containers.
Is running as root always wrong?
It is a best practice to set runAsNonRoot: true. The checker flags containers that run as root or have no securityContext configured.
Does this connect to a cluster?
No. Paste your YAML; everything is analysed in your browser and nothing is uploaded.
How do I fix the findings?
Add resources.requests/limits, liveness/readiness probes, and a securityContext with runAsNonRoot: true to each container.