From b5c7c2549f78f65bda88e11aabe19f9835c85880 Mon Sep 17 00:00:00 2001 From: Ian Howell Date: Thu, 25 Apr 2019 14:12:56 -0500 Subject: [PATCH] Update documentation to reflect changes to subchart schemas Signed-off-by: Ian Howell --- docs/charts.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/charts.md b/docs/charts.md index b53f78c4a..442269e55 100644 --- a/docs/charts.md +++ b/docs/charts.md @@ -841,6 +841,12 @@ protocol: https helm install --set port=443 ```` +Furthermore, the final `.Values` object is checked against *all* subchart +schemas. This means that restrictions on a subchart can't be circumvented by a +parent chart. This also works backwards - if a subchart has a requirement that +is not met in the subchart's `values.yaml` file, the parent chart *must* +satisfy those restrictions in order to be valid. + ### References When it comes to writing templates, values, and schema files, there are several