1 of 3
Deployment/web
Holds
That’s the difference.
yamllint tells you your YAML is valid. It will not tell you it is a valid k8s manifest. A missing field, a wrong type or an indentation that changes the structure all pass syntax and break the deploy. We read the state of every document instead.
The shelfFig. 1
A glaze can look finished at the rim and still be running at the foot. So can a manifest. Every document in the stream is shown as a piece on the shelf, and how far its glaze has run is how far the defect has travelled.
1 of 3
Deployment/web
Holds
2 of 3
Ingress/web
Runs
3 of 3
ConfigMap/web
Holds
Illustrative file The validator is not built yet. This shelf shows the state vocabulary it will return.
Two firingsFig. 2
Both panels carry the same Ingress manifest in full, all fourteen lines. The only difference is what each run is looking at.
yamllint · syntax Holds
1 | apiVersion: networking.k8s.io/v1 2 | kind: Ingress 3 | metadata: 4 | name: web 5 | spec: 6 | rules: 7 | - http: 8 | paths: 9 | - path: / 10 | pathType: Prefix 11 | backend: 12 | service: 13 | name: web 14 | port: {number: 80}
No output, no error, exit code 0. The file is valid YAML, so the pipeline goes green and the shelf looks clean.
YAML Validator · schema Runs
1 | apiVersion: networking.k8s.io/v1 2 | kind: Ingress 3 | metadata: 4 | name: web 5 | spec: 6 | rules: 7 | - http: | host: <missing> 8 | paths: 9 | - path: / 10 | pathType: Prefix 11 | backend: 12 | service: 13 | name: web 14 | port: {number: 80}
Same file, same fourteen lines, with spec.rules[0] missing required field host. Caught before the deploy.
Run risk
HoldsMediumFuses
Assessed from the field path, the depth of the document and whether the resource reaches production. A missing host on an Ingress is never cosmetic: the route resolves to nothing.
Where it sits
Position is reported the way the file is written: spec, then rules[0], then the field. Not a line number you have to go and find.
Illustrative output The validator is not built yet. This is the error format it will return.
Field notesFig. 3
RecipeFig. 4
The formulation confirmed for the private beta. Nothing in this table is built yet.
| Ingredient | What it does | Fires in |
|---|---|---|
| Per-field errors with a real path | Names the field, the path and the fix: spec.rules[0] is missing required field 'host', not “expected block end”. | API, browser, Action |
| JSON Schema 2020-12 and k8s CRDs | Checks structure against a real schema instead of checking that the file parsed. | All surfaces |
| Built-in k8s schemas | Deployment, Service, Ingress, ConfigMap and Secret, with no setup. | Built in |
| Custom schemas | Upload and reference schemas for your own resources and internal manifests. | Browser |
| Pipeline gate | POST /v1/validate returns structured errors a CI job can fail on. | API |
| GitHub Action | Runs the same check on pull requests and comments the failing path on the diff. | CI |
| Browser paste tool | Paste a manifest and read per-field errors. Your file is processed locally and never uploaded. | Browser |
| Team workspaces | Shared schemas and org-wide validation policies, at the paid tier. | Dashboard |
Quick noteFig. 5
Your file is never uploaded. The browser tool reads manifests locally, so there is no server round trip for your YAML and nothing to opt out of later. We will show you a working demo first.