[deathanatos]

> See, there is no general schema for what goes and doesn't go inside a values.yaml file. Thus, your development environment cannot help you beyond basic YAML syntax highlighting.

… this is just an odd complaint. Naturally, there isn't a schema — there inherently cannot be one. Values are the options for the app at hand; they're naturally dependent on the app.

> but without any schema validation!

I have seen people supply JSON schemas for values with the chart. I appreciate that.

Of all the pitfalls … the clunky stringly-typed "manipulate YAML with unsafe string templating" is the biggest pitfall, to me…

[everforward]

A lot of those values end up being used in places that do have schemas. I think they're asking for what is basically inferred types.

They want Helm to recognize that the cpuLimit value is used as a CPU limit for a Pod and throw errors for any cpuLimit that isn't a valid CPU limit.

Agreed that the user will have to write their own schema for CLI arguments.