yaml

TL;DR: While YAML relies on strict indentation and external templating engines for container manifests, HCL provides native logic and block structures for infrastructure definition.

YAML (or YAML Ain’t Markup Language): Many compare YAML to JSON or XML formats. I prefer to compare it with HCL (HashiCorp Configuration Language).

• YAML (Data-First): Excellent for declarative configuration state files (like Kubernetes manifests or Ansible playbooks). However, its strict sensitivity to indentation and lack of native logic or modular constructs can make large, complex configurations difficult to maintain and prone to silent formatting errors.
• HCL (Infrastructure-First): Purpose-built for Infrastructure as Code (IaC) tools like Terraform and OpenTofu. HCL uses explicit block structures {} instead of strict indentation, making it easier to read and parse. Crucially, HCL includes built-in expression evaluation, variables, conditional logic, and modular references out-of-the-box.

While YAML remains the universal standard across Kubernetes manifests and CI/CD pipelines, HCL offers a far cleaner and more powerful experience when defining complex cloud infrastructure.

Example

Declaration

YAML

name: web-server
port: 8080

HCL

name = "web-server"
port = 8080

Multiline

YAML

script: |
  echo "Line 1"
  echo "Line 2"

One Line in multiline formats

YAML

description: >
  This is a very long sentence that spans across multiple lines
  in the YAML source file for readability, but renders as a single line.

HCL (There is no direct equivalent in HCL on both.)

Templating & Interpolation: External Engine vs. Native First-Class Feature

YAML

metadata:
  name: "{{ .Values.appName }}-service"

HCL

metadata {
  name = "${var.app_name}-service"
}

or

name = var.app_name

YAML is widely used in container configuration (e.g., Docker, Kubernetes). How can we distinguish between a Docker Compose file and a Kubernetes manifest file?

Docker Compose YAML

YAML

version: '3.8'
services:
  web:
    image: nginx:latest
    ports:
      - "8080:80"

Kubernetes Manifest YAML

YAML

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-deployment
spec:
  replicas: 3

I think the examples here speak for themselves.

Back to Certified Cloud Native Platform Engineering Associate Preparation