KYAML in CI/CD: formatting advances only when the object remains equal

The signal and the facts that change the decision

KYAML reduces syntactic freedom in Kubernetes output, but reformatting repositories can touch templates, comments, linters, and diffs. The central test is semantic equality of the object, not visual appeal.

Every valid KYAML document is valid YAML, but not every YAML document already follows the KYAML subset. kubectl supports KYAML output; this does not require accepting KYAML as source across the toolchain.

Helm and generators should be tested at source and render because whitespace may matter in templates. A mass conversion can lose comments, change templates, or mix functional change into an avalanche of diffs.

Decision, limits, and stop condition

Introduce KYAML as inspection output and in one pilot directory before changing sources or team preferences.

A mass conversion can lose comments, change templates, or mix functional change into an avalanche of diffs.

Execution and proof of completion

Execution should start by selecting representative simple manifests, helm, and crds. Then, comparing canonical objects before/after and running schema, policy, and dry-run. Closure requires separating the formatting commit from any api or value change.

The pilot passes with equal object, preserved comments, green toolchain, and clearer human review.

• selecting representative simple manifests, Helm, and CRDs.
• comparing canonical objects before/after and running schema, policy, and dry-run.
• separating the formatting commit from any API or value change.
• The pilot passes with equal object, preserved comments, green toolchain, and clearer human review.