How do you safely convert YAML to JSON for Kubernetes ConfigMaps?

[coderaviverma]

In Kubernetes and Helm charts, configuration is often authored in YAML
(values.yaml, templates), but many applications still expect JSON at runtime.

This raises a common question:

What’s the safest way to convert YAML → JSON when mounting configs
via ConfigMaps, without introducing subtle bugs?

From experience, common pitfalls include:

• duplicate keys silently overriding values
• indentation errors that pass YAML parsing
• anchors/aliases behaving differently across parsers
• inconsistent results between Helm toJson, yq, and runtime tooling

I’m curious how others handle this in production:

• convert during Helm templating?
• convert at build time in CI?
• convert at runtime in the container?
• or avoid conversion entirely?

Would love to hear best practices and real-world setups.

[coderaviverma]

For quick validation or debugging, I’ve been using:
https://jsonviewertool.com/yaml-to-json

It’s client-side only and helpful to catch duplicate keys
before they hit CI or Kubernetes.