From 432fd9c110bf75de46cfc8db4748ad0a0fdc28fd Mon Sep 17 00:00:00 2001 From: Taylor Thomas Date: Thu, 31 Oct 2019 09:26:22 -0600 Subject: [PATCH] fix(cmd): Updates description for template validation flag This is a follow up to discussion in #6663 that clarifies exactly what the validate flag is doing. It isn't meant to be a generic schema validator, but rather validates the manifests against the current cluster as if it was going to be installing them. Signed-off-by: Taylor Thomas --- cmd/helm/template.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/helm/template.go b/cmd/helm/template.go index 1c6d88ee8..5312d798f 100644 --- a/cmd/helm/template.go +++ b/cmd/helm/template.go @@ -119,7 +119,7 @@ func newTemplateCmd(cfg *action.Configuration, out io.Writer) *cobra.Command { addInstallFlags(f, client, valueOpts) f.StringArrayVarP(&showFiles, "show-only", "s", []string{}, "only show manifests rendered from the given templates") f.StringVar(&client.OutputDir, "output-dir", "", "writes the executed templates to files in output-dir instead of stdout") - f.BoolVar(&validate, "validate", false, "establish a connection to Kubernetes for schema validation") + f.BoolVar(&validate, "validate", false, "validate your manifests against the Kubernetes cluster you are currently pointing at. This is the same validation performed on an install") f.StringArrayVarP(&extraAPIs, "api-versions", "a", []string{}, "Kubernetes api versions used for Capabilities.APIVersions") return cmd