Fairway v3.0.0: charts validate their own values

Fairway v3.0.0 is out, and every generated chart now ships a values.schema.json. Helm reads it automatically on install, upgrade, template, and lint, catching bad values before they reach a cluster:

• Typo’d or unknown keys fail fast instead of being silently dropped.
• Out-of-range and out-of-set values are rejected at deploy time.
• The merged values are checked — values.yaml plus every -f file and --set flag.

This is a major release for a reason: a deploy that passed on an earlier version in spite of a typo’d key will fail once you regenerate your chart with 3.0. That is the point — but treat the upgrade as a chance to surface overrides you did not know were being ignored, and port any such value to a supported field.

If there is no supported field for something you need, file a Chart Template Extension Request so the road can be paved for it — the custom key stays open in the meantime.

See the Fairway component page and the manifest schema reference for background on how charts are generated.