Skip to content
Testaroo
yaml718 B

Kubernetes Kustomization Overlay

A Kustomize overlay with a name prefix and suffix, common labels, an image tag override, a configMapGenerator merge, and a JSON-6902 patch embedded as a block scalar: YAML inside YAML, which naive rewriters mangle.

Config testingConfig parsingEditor testing
Preview, first 39 linesyaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: example-apps
namePrefix: prod-
nameSuffix: -v2

commonLabels:
  app.kubernetes.io/instance: prod
  app.kubernetes.io/managed-by: kustomize

resources:
  - ../../base
  - networkpolicy.yaml

patches:
  - target:
      kind: Deployment
      name: orders
    patch: |
      - op: replace
        path: /spec/replicas
        value: 6
      - op: add
        path: /spec/template/spec/containers/0/env/-
        value:
          name: TIER
          value: prod

configMapGenerator:
  - name: orders-config
    behavior: merge
    literals:
      - LOG_LEVEL=warn

images:
  - name: registry.example.invalid/example-org/orders
    newTag: 1.4.0

Specifications

Kind
Kustomization
Resources
2
Patches
1
Patch Ops
2
Image Overrides
1
Has Embedded Patch Scalar
true

Testing contract

Expected to pass
Scenario
Apply a Kustomize overlay whose patch is embedded as a YAML block scalar
Expected result
The embedded patch parses as two JSON-6902 operations and the replica count for the orders Deployment becomes 6

What is a .yaml file?

YAML (YAML Ain't Markup Language) is a human-readable data-serialization format using indentation, key-value pairs, and lists, and is a superset of JSON. It supports comments, anchors, and multiple documents per file, favoring readability for configuration. Its indentation sensitivity makes it error-prone to hand-edit.

How to use this file

Use an example YAML file to test config parsers, indentation and anchor handling, multi-document streams, and safe-loading to avoid arbitrary object construction.

How to use this file for testing

“Kubernetes Kustomization Overlay” is a deterministic Testaroo fixture for Config testing, Config parsing, Editor testing. TOML, INI, YAML, .env, and dotfile configuration samples with nested sections and typed values, for testing config parsers, loaders, and environment tooling.

Documented properties for this file: YAML · 718 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.

Code examples

import yaml  # pip install pyyaml

with open("kustomization.yaml") as f:
    data = yaml.safe_load(f)
print(data)

Generated by generation/pipelines.py. Free for any use, no attribution required, license.

Related files