Loading...
The human-readable text format in which modern infrastructure is described and deployed.
Quick Definition
YAML is a human-readable data format widely used for configuration in cloud-native tooling, defining Kubernetes manifests, CI/CD pipelines, and Infrastructure as Code. Its clarity makes it the default for declarative configuration, though indentation errors are a common pitfall.
YAML is a plain-text format for structured data, designed to be readable by humans first: indentation shows hierarchy, and there are no brackets or closing tags. It has become the default language of infrastructure configuration, Kubernetes manifests, CI/CD pipelines, and deployment definitions are overwhelmingly written in YAML.
Its significance is bigger than syntax: YAML files are where infrastructure decisions become text. A container's CPU request, a cluster's node count, an autoscaler's limits, all sit in YAML, which means they can be version-controlled, code-reviewed, and policy-checked before they cost anything.
Example. A reviewer scanning a Kubernetes manifest spots a memory request of 64Gi where 4Gi was intended. The typo dies in code review. Deployed, it would have forced the cluster to add expensive nodes within the hour.
The same readability that makes YAML approachable makes it error-prone: indentation mistakes and type quirks are classics. Validation in the pipeline and policy as code rules that flag expensive values turn YAML review into a genuine cost control point. The Kubernetes best practices guide treats manifest hygiene as a first-class discipline.
YAML Ain't Markup Language, a recursive joke emphasizing that it stores data rather than marking up documents.
Readability. Configuration is read far more often than written, and YAML's clean structure suits files humans must review and reason about.
Resource sizes and scaling limits live in YAML. Reviewing and policy-checking those values catches expensive mistakes before deployment.