How to use this developer tool
- Paste the requested YAML or key/value input.
- Adjust the available options for the target output.
- Select Validate Manifests or press Ctrl/Cmd + Enter.
- Review findings, then copy or download the result.
Kubernetes YAML Validator
Run a fast structural review on one or more Kubernetes YAML manifests. The validator separates multi-document input, checks required identity fields and metadata, and applies focused checks for common workload and Service mistakes. Processing stays in the browser. The findings complement kubectl server-side validation, which is still needed for cluster APIs, admission policies, and custom resources.
Developer Input
YAML or line inputAd space
What this developer tool does
Validates YAML syntax and baseline Kubernetes structure, then applies kind-aware checks for Deployments, StatefulSets, DaemonSets, Pods, Services, ConfigMaps, and Secrets.
Each non-empty YAML document must contain apiVersion, kind, and metadata.name. Workloads are checked for pod templates and containers; selectors are compared with template labels when available.
The result is generated locally and should be reviewed before deployment.
Example
The Sample button loads a representative input. Running it produces the same structured output displayed in the result panel, including counts and any findings.
apiVersion: apps/v1
kind: Deployment
metadata:
name: web-app
spec:
replicas: 2
selector:
matchLabels:
app: web
template:
metadata:
labels:
app: web
spec:
containers:
- name: web
image: nginx:1.27Use cases
- Pre-commit configuration review
- Pull request documentation
- Migration inventory preparation
- Training and troubleshooting
Tips for reliable output
- Use spaces instead of tab indentation in YAML.
- Keep multi-document separators on their own line.
- Review generated files before applying them.
- Confirm static findings with official CLI validation.
- Avoid pasting production secrets into shared devices.
Processing details
Each non-empty YAML document must contain apiVersion, kind, and metadata.name. Workloads are checked for pod templates and containers; selectors are compared with template labels when available.
This is not an OpenAPI or admission-controller validator. It cannot know installed CRDs, cluster versions, RBAC, quotas, or policy webhooks.
Frequently asked questions
Can this Kubernetes YAML validator check multiple documents separated by ---?
The result follows the static rules described on this page. Review finding 1 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Does it validate custom resources against installed CRD schemas?
The result follows the static rules described on this page. Review finding 2 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Why should I still use kubectl apply --dry-run=server?
The result follows the static rules described on this page. Review finding 3 in context and confirm it with the relevant Docker or Kubernetes command before deployment.
Does the validator decode or upload Kubernetes Secret data?
Input is processed in your browser. The page does not make a network request with the configuration, but downloaded output and browser history should still be handled according to your security policy.
Which workload selector and pod template mistakes are detected?
The result follows the static rules described on this page. Review finding 5 in context and confirm it with the relevant Docker or Kubernetes command before deployment.