Helm Lint

helm lint

examine a chart for possible issues

Synopsis

This command takes a path to a chart and runs a series of tests to verify that the chart is well-formed.

If the linter encounters things that will cause the chart to fail installation, it will emit [ERROR] messages. If it encounters issues that break with convention or recommendation, it will emit [WARNING] messages.

  1. helm lint PATH [flags]

Options

  1.   -h, --help                      help for lint
  2.       --kube-version string       Kubernetes version used for capabilities and deprecation checks
  3.       --quiet                     print only warnings and errors
  4.       --set stringArray           set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  5.       --set-file stringArray      set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
  6.       --set-json stringArray      set JSON values on the command line (can specify multiple or separate values with commas: key1=jsonval1,key2=jsonval2)
  7.       --set-literal stringArray   set a literal STRING value on the command line
  8.       --set-string stringArray    set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  9.       --skip-schema-validation    if set, disables JSON schema validation
  10.       --strict                    fail on lint warnings
  11.   -f, --values strings            specify values in a YAML file or a URL (can specify multiple)
  12.       --with-subcharts            lint dependent charts

Options inherited from parent commands

  1.       --burst-limit int                 client-side default throttling limit (default 100)
  2.       --debug                           enable verbose output
  3.       --kube-apiserver string           the address and the port for the Kubernetes API server
  4.       --kube-as-group stringArray       group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  5.       --kube-as-user string             username to impersonate for the operation
  6.       --kube-ca-file string             the certificate authority file for the Kubernetes API server connection
  7.       --kube-context string             name of the kubeconfig context to use
  8.       --kube-insecure-skip-tls-verify   if true, the Kubernetes API server's certificate will not be checked for validity. This will make your HTTPS connections insecure
  9.       --kube-tls-server-name string     server name to use for Kubernetes API server certificate validation. If it is not provided, the hostname used to contact the server is used
  10.       --kube-token string               bearer token used for authentication
  11.       --kubeconfig string               path to the kubeconfig file
  12.   -n, --namespace string                namespace scope for this request
  13.       --qps float32                     queries per second used when communicating with the Kubernetes API, not including bursting
  14.       --registry-config string          path to the registry config file (default "~/.config/helm/registry/config.json")
  15.       --repository-cache string         path to the directory containing cached repository indexes (default "~/.cache/helm/repository")
  16.       --repository-config string        path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 11-Sep-2024