Kubernetes YAML Analyzer
Validate and analyze Kubernetes manifests for common issues.
Last reviewed by the Radiatus Cloud team
Kubernetes YAML Configuration
Issues Found
Best Practice Recommendations
Security Considerations
Want this automated for your stack?
We build CI/CD, Kubernetes & IaC pipelines that scale.
Check a manifest before applying it
A Kubernetes manifest with a subtle error can be accepted and then behave in ways you did not intend, or be rejected after you have already scripted around it. This analyser validates and reviews Kubernetes manifests for common issues, so you catch problems before applying them to a cluster.
The issues that slip through
Manifests fail in characteristic ways: a mismatched label selector so a service reaches no pods, missing resource requests so scheduling is unpredictable, an image tag that is mutable, a typo in a field name that is silently ignored, or a probe misconfigured so a healthy pod is killed. These are valid YAML and often valid Kubernetes, yet wrong in effect. Reviewing for them catches the gap between what the manifest says and what you meant.
A pre-apply review, kept local
Checking a manifest before it reaches the cluster is faster and safer than debugging a misbehaving workload afterward. The analysis runs entirely in your browser, so your configuration is never uploaded, which matters when it describes your own infrastructure.
Related tools
- CI/CD Security Gap Analyzer — Checklist based analyzer for CI/CD pipeline security gaps.
- Docker Security Scanner — A new tool extracted from the codebase.
- Terraform Scanner — A new tool extracted from the codebase.
- SQL Formatter — Format and indent SQL queries for readability. Handles joins, subqueries and CTEs, supports common dialects, and runs entirely in your browser.
Frequently Asked Questions
What issues does it catch?
Common manifest problems like mismatched label selectors, missing resource requests, mutable image tags, ignored field typos and misconfigured health probes.
Why can a valid manifest still be wrong?
Because it can be valid YAML and valid Kubernetes yet not do what you intended, such as a selector that matches no pods. The analyser checks effect, not just syntax.
Why do resource requests matter?
Because without them the scheduler cannot place pods predictably, leading to overcommitted nodes and unstable behaviour. Requests make scheduling deterministic.
Is this checking my live cluster?
No. It reviews the manifests you provide, before you apply them, so problems are caught early.
Is my configuration uploaded?
No. The analysis runs entirely in your browser.
Privacy & Security
Analysis happens locally.
About This Tool
This tool runs entirely in your browser. No data is sent to any server, ensuring complete privacy. Simply use the interface above to get started — no registration or login required.
Disclaimer: This tool is provided "as is" without warranty of any kind. Results are for educational and utility purposes.