How to use Kubernetes and CI YAML Checker
- Choose Selected Kubernetes resources or GitHub Actions workflow subset.
- Paste your YAML, or choose one UTF-8 document file to replace the text. Kubernetes mode accepts a stream of supported resource documents; GitHub mode accepts one workflow.
- Read each finding’s document number, path and severity. Unsupported structures need separate review; an empty findings table does not establish that a deployment will work.
- Download yaml-structural-review.json to keep the named ruleset, resource or job records and findings. Test the final configuration in its intended cluster or workflow runner.
Example: Kubernetes and CI YAML Checker
Review a Pod whose image uses a tag and whose container has no resource requests or limits.
Options
- Selected Kubernetes resources
- The checker recognizes v1 Pod, Service and ConfigMap, and apps/v1 Deployment. Selected checks cover resource names, container declarations, ports, security flags, resource declarations and Deployment selector labels. It does not parse quantity values or validate complete per-kind schemas.
- GitHub Actions workflow subset
- Review trigger structure, selected permissions, runner and step declarations, and whether remote actions use full commit pins. Reusable workflow calls, matrix behavior and expression evaluation are outside the subset. The checker never runs shell commands or fetches actions.
- Dated findings
- The rulesets are dated 3 October 2026. Review findings identify settings such as an unpinned image or broad permission; they are not all syntax errors. Unsupported items describe gaps in coverage, not a successful validation.
Supported inputs and limits
- YAML input is limited to 100,000 UTF-8 bytes, 5,000 lines, 20 documents, 20,000 value nodes and 32 levels.
- Each document must be a plain mapping.
- Anchors, aliases, merge keys, explicit tags, directives and repeated keys are refused.
- GitHub mode accepts one workflow with 1 to 50 jobs and up to 100 steps per steps job;
- Pod container lists and Service ports are capped at 50.
More details
The check stops above 200 findings.
Rules are a dated structural subset: no cluster admission, complete schemas, action verification, expression execution, quantity comparisons or GitLab validation.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Valid YAML and operational validity differ
A YAML document can parse while using an unavailable API version, action or runtime value. This page does not contact a cluster, validate complete schemas or execute workflow expressions. Review the dated coverage and test the intended configuration in its own platform. Do not copy a structural pass as a deployment or security approval.
Questions about Kubernetes and CI YAML Checker
Does this replace cluster or workflow validation?
No. Platform-specific validation and actual execution still need separate checks.
Are shell commands or actions executed?
No. They remain text in the submitted YAML.
Can I check a GitLab pipeline?
No. The CI checks here target the supported GitHub Actions structure.