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.

  1. helm template [NAME] [CHART] [flags]

Options

  1. -a, --api-versions stringArray Kubernetes api versions used for Capabilities.APIVersions
  2. --atomic if set, the installation process deletes the installation on failure. The --wait flag will be set automatically if --atomic is used
  3. --ca-file string verify certificates of HTTPS-enabled servers using this CA bundle
  4. --cert-file string identify HTTPS client using this SSL certificate file
  5. --create-namespace create the release namespace if not present
  6. --dependency-update update dependencies if they are missing before installing the chart
  7. --description string add a custom description
  8. --devel use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
  9. --disable-openapi-validation if set, the installation process will not validate rendered templates against the Kubernetes OpenAPI Schema
  10. --dry-run simulate an install
  11. -g, --generate-name generate the name (and omit the NAME parameter)
  12. -h, --help help for template
  13. --include-crds include CRDs in the templated output
  14. --insecure-skip-tls-verify skip tls certificate checks for the chart download
  15. --is-upgrade set .Release.IsUpgrade instead of .Release.IsInstall
  16. --key-file string identify HTTPS client using this SSL key file
  17. --keyring string location of public keys used for verification (default "~/.gnupg/pubring.gpg")
  18. --kube-version string Kubernetes version used for Capabilities.KubeVersion
  19. --name-template string specify template used to name the release
  20. --no-hooks prevent hooks from running during install
  21. --output-dir string writes the executed templates to files in output-dir instead of stdout
  22. --pass-credentials pass credentials to all domains
  23. --password string chart repository password where to locate the requested chart
  24. --post-renderer postRendererString the path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path
  25. --post-renderer-args postRendererArgsSlice an argument to the post-renderer (can specify multiple) (default [])
  26. --release-name use release name in the output-dir path.
  27. --render-subchart-notes if set, render subchart notes along with the parent
  28. --replace re-use the given name, only if that name is a deleted release which remains in the history. This is unsafe in production
  29. --repo string chart repository url where to locate the requested chart
  30. --set stringArray set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  31. --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)
  32. --set-string stringArray set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  33. -s, --show-only stringArray only show manifests rendered from the given templates
  34. --skip-crds if set, no CRDs will be installed. By default, CRDs are installed if not already present
  35. --skip-tests skip tests from templated output
  36. --timeout duration time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
  37. --username string chart repository username where to locate the requested chart
  38. --validate validate your manifests against the Kubernetes cluster you are currently pointing at. This is the same validation performed on an install
  39. -f, --values strings specify values in a YAML file or a URL (can specify multiple)
  40. --verify verify the package before using it
  41. --version string specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used
  42. --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
  43. --wait-for-jobs if set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout

Options inherited from parent commands

  1. --debug enable verbose output
  2. --kube-apiserver string the address and the port for the Kubernetes API server
  3. --kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  4. --kube-as-user string username to impersonate for the operation
  5. --kube-ca-file string the certificate authority file for the Kubernetes API server connection
  6. --kube-context string name of the kubeconfig context to use
  7. --kube-token string bearer token used for authentication
  8. --kubeconfig string path to the kubeconfig file
  9. -n, --namespace string namespace scope for this request
  10. --registry-config string path to the registry config file (default "~/.config/helm/registry/config.json")
  11. --repository-cache string path to the file containing cached repository indexes (default "~/.cache/helm/repository")
  12. --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 18-May-2022