The useful shift
KYAML's promotion brings attention to a mundane but important problem: YAML is easy to edit while being hard to review as an operational object. Platform teams need a path from a proposed manifest change to a validated, understandable deployment change.
Build checks in layers
Format and parse first. Then validate schema, policy intent, and environment-specific references. Render the final object that the cluster will receive and include that render in code review. Admission control remains valuable, but it should be a final barrier rather than the first time an invalid assumption is discovered.
Review semantics, not whitespace
Ask whether a diff changes ownership, network exposure, privilege, resource limits, or rollout behavior. Tie each class to tests and an owner. This makes the review conversation about system effect rather than formatting preference and gives incident responders a clearer record of why a change passed.
FAQ
Does validation replace admission control? No; local checks improve feedback while admission protects the running cluster. Where should the workflow start? With the smallest service whose rendered manifests can be tested in CI.