Helm LogoDocs

 

Helm Template

helm template

locally render templates

Synopsis

Render chart templates locally and display the output.

Any values that would normally be looked up or retrieved in-cluster will be faked locally. Additionally, none of the server-side testing of chart validity (e.g. whether an API is supported) is done.

helm template [NAME] [CHART] [flags]

Options

  -a, --api-versions stringArray   Kubernetes api versions used for Capabilities.APIVersions
      --atomic                     if set, installation process purges chart on fail. The --wait flag will be set automatically if --atomic is used
      --ca-file string             verify certificates of HTTPS-enabled servers using this CA bundle
      --cert-file string           identify HTTPS client using this SSL certificate file
      --dependency-update          run helm dependency update before installing the chart
      --devel                      use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
      --dry-run                    simulate an install
  -g, --generate-name              generate the name (and omit the NAME parameter)
  -h, --help                       help for template
      --key-file string            identify HTTPS client using this SSL key file
      --keyring string             location of public keys used for verification (default "~/.gnupg/pubring.gpg")
      --name-template string       specify template used to name the release
      --no-hooks                   prevent hooks from running during install
      --output-dir string          writes the executed templates to files in output-dir instead of stdout
      --password string            chart repository password where to locate the requested chart
      --render-subchart-notes      if set, render subchart notes along with the parent
      --replace                    re-use the given name, only if that name is a deleted release which remains in the history. This is unsafe in production
      --repo string                chart repository url where to locate the requested chart
      --set stringArray            set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --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)
      --set-string stringArray     set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  -s, --show-only stringArray      only show manifests rendered from the given templates
      --skip-crds                  if set, no CRDs will be installed. By default, CRDs are installed if not already present
      --timeout duration           time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
      --username string            chart repository username where to locate the requested chart
      --validate                   validate your manifests against the Kubernetes cluster you are currently pointing at. This is the same validation performed on an install
  -f, --values strings             specify values in a YAML file or a URL(can specify multiple)
      --verify                     verify the package before installing it
      --version string             specify the exact chart version to install. If this is not specified, the latest version is installed
      --wait                       if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout

Options inherited from parent commands

      --add-dir-header                   If true, adds the file directory to the header
      --alsologtostderr                  log to standard error as well as files
      --debug                            enable verbose output
      --kube-context string              name of the kubeconfig context to use
      --kubeconfig string                path to the kubeconfig file
      --log-backtrace-at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log-dir string                   If non-empty, write log files in this directory
      --log-file string                  If non-empty, use this log file
      --log-file-max-size uint           Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                      log to standard error instead of files (default true)
  -n, --namespace string                 namespace scope for this request
      --registry-config string           path to the registry config file (default "~/.config/helm/registry.json")
      --repository-cache string          path to the file containing cached repository indexes (default "~/.cache/helm/repository")
      --repository-config string         path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")
      --skip-headers                     If true, avoid header prefixes in the log messages
      --skip-log-headers                 If true, avoid headers when opening log files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
  -v, --v Level                          number for the log level verbosity
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 4-Feb-2020