[ofrzeta]

It's just easier to shoot yourself in the foot with no proper type support (or enforcement) in YAML. I've seen Kubernetes updates fail when the version field was set to 1.30 and it got interpreted as a float 1.3. Sure, someone made a mistakes but the config language should/could stop you from making them.

[XorNot]

Yeah but that's on the application schema. If it's version string why are accepting floats for it?

[ikiris]

so use json?

[Too]

It allows the exact same problem. version: 1.30 vs version: "1.30".

[Sayrus]

Helm supports typing the values passed to the Chart but most charts aren't providing it. Most fields within out-of-the-box Kubernetes resources are using well-defined typed.

As much as Helm is prone to some type of errors, it will validate the schema before doing an install or upgrade so `version: 1.30` won't apply but `version: "1.30"` will.