Kubernetes 1.37 KYAML Fix Exposed: Null Values Still Silently Deleted on Apply
Kubernetes 1.37 introduced KYAML (KEP-5295) as a stricter YAML dialect aimed at eliminating long-standing YAML 1.1 parsing bugs, such as unquoted country codes like 'NO' being misread as boolean false. A hands-on test against a live 1.37.0 API server using 13 hand-crafted ConfigMap manifests revealed that 12 out of 13 ambiguous values caused failures of some kind. Boolean-looking and number-like values triggered loud server-side rejections, preventing silent data corruption in those cases. However, null-equivalent values — specifically 'null' and '~' — were accepted without error, but their corresponding keys were silently dropped from the stored ConfigMap entirely. This means KYAML addresses some YAML ambiguity issues but does not yet protect against data loss when null-type values are applied to a live cluster.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in