Invalid `schema` parameter for VM cluster chart about helm-charts

[Haleygo]

Hi @MisguidedEmails ,
Thanks for the fix!

Note: May be worth having some sort of schema validation (or dry/actual run against a kind cluster or something) to catch oversights like this.

Indeed, there is a chart installation test on several k8s versions, to ensure each chart can be installed successfully with default values, but this was missing because it's triggered by specific value(

[MisguidedEmails]

Indeed, there is a chart installation test on several k8s versions, to ensure each chart can be installed successfully with default values, but this was missing because it's triggered by specific value

Hrm, but it's rendered by default? No specific values are required to present this problem (since it's an if/else). It seems like the pipeline might not be catching those type of errors. If I do a helm template . on the pre-fix code, it outputs the invalid tcpSocket with no additional values presented.

[MisguidedEmails]

Interesting, a helm install doesn't appear to care? But it is invalid. helm install vm-test . installs fine, ignoring that invalid part, but helm install vm-test --dry-run shows that the scheme: is there.

[MisguidedEmails]

@Haleygo - I've raised #852 as a fix for the problem. Since helm doesn't appear to error on invalid manifests, and neither do the chart testing or helm lint tools. Using kubectl appears to be the only option.

I'll close this issue, since the original problem is fixed.